| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
data access errors when trying to read/write to non-existant PCI devices.
fix the psycho bridge to use peek for probing devices. This no longer
fakes it if the OFW node doesn't exist (and the reg == 0).
Reviewed by: jake, tmm
|
|
|
|
| |
vm_fault(); remove a pointless assignment statement from that path.
|
|
|
|
|
|
|
|
|
|
| |
when serving up more than about 32 active files. For details see
section 6.3 (pg 111) of Daniel Ellard and Margo Seltzer, ``NFS
Tricks and Benchmarking Traps'' in the Proceedings of the Usenix
2003 Freenix Track, June 9-14, 2003 pg 101-114.
Obtained from: Daniel Ellard <ellard@eecs.harvard.edu>
Sponsored by: DARPA & NAI Labs.
|
|
|
|
| |
of indentation a bit.
|
| |
|
|
|
|
|
| |
- Assert that the vm object and its backing vm object are both locked in
vm_object_qcollapse().
|
|
|
|
|
| |
us to skip the pctcpu_update() call which lead to inaccurate cpu usage
statistics for processes that didn't run often.
|
|
|
|
|
|
| |
causing poor interactive performance while unnice processes were running.
The new scheme still allows nice to have an effect on priority but it is
not as dramatic as the effect of the interactivity score.
|
| |
|
|
|
|
|
| |
Submitted by: Christian S.J. Peron <maneo@bsdpro.com>
PR: kern/53557
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Avoid calling bread() with different sizes on the same blkno.
Although the buffer cache is designed to handle differing size
buffers, it erroneously tries to write the incorrectly-sized buffer
buffer back to disk before reading the correctly-sized one, even
when it's not dirty. This behaviour caused a panic for read-only
NTFS mounts when INVARIANTS was enabled ("bundirty: buffer x still
on queue y"), reported by NAKAJI Hiroyuki.
- Fix a bug in the code handling holes: a variable was incremented
instead of decremented, which could cause an infinite loop.
|
|
|
|
|
|
|
| |
This saves much KVA for vm_pages and you don't need to increase NKPT
for large physical memory anymore.
Suggested by: dfr
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
for vnodes reached through double indirection (i.e. **vpp). This
is worked-around by special-casing the identifier "vpp" (adding one
level of indirection).
The alternative fix mentioned in the PR had required substantial
changes to this script.
In case there are locking violations that had been hidden without
this patch, they may suddenly show up, now ...
This change does not affect code compiled without DEBUG_VFS_LOCKS.
PR: kern/46652
|
|
|
|
|
|
|
|
| |
before calling it for bound thread. To avoid this problem, change
thread_schedule_upcall to not put new thread on run queue, let caller
do it, so we can tweak the new thread before setting it to run.
Reported by: pho
|
|
|
|
| |
works anyway.
|
| |
|
| |
|
|
|
|
|
| |
#ifdef DIAGNOSTIC hold a mutex while calling callout's so that we hear
about it if they sleep.
|
|
|
|
|
| |
Move initialization of DTYPE_VNODE specific field f_seqcount into
the DTYPE_VNODE specific code.
|
|
|
|
| |
Order the fields in struct file in sections after their scope.
|
|
|
|
| |
an int.
|
|
|
|
|
|
|
| |
the vm map lock. What's really needed is vm object locking, which
is (for the moment) provided Giant.
Reviewed by: tegge
|
|
|
|
|
|
|
| |
threads in the process have already masked the signal, so job control
is delayed. But later a thread unmasking the STOP signal should enable
job control, so in issignal(), scanning all threads in process to see
if we can direct suspend some of them, not just suspend current thread.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
we can deadlock because of lock order reversals. This was not
caught because Witness ignores pool mutexes right now.
Diagnosis and help: truckman
Noticed by: pho
|
| |
|
| |
|
|
|
|
| |
HW sponsored by: Martin Blapp <mbr@FreeBSD.ORG>
|
|
|
|
|
| |
You may still need to increase NKPT for larger memory.
I have successfully booted 8GB system with NKPT=256.
|
| |
|
|
|
|
|
|
|
|
|
| |
"maxproc limit exceeded by uid %i, please see tuning(7) and login.conf(5)."
Which will be triggered whenever a user hits his/her maxproc limit or
the systemwide maxproc limit is reached.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
- Don't require all receivers of ipis to wait for all other receivers,
only that the sender wait for all receivers. This should reduce the
amount of time spent with interrupts disabled, which may be a cause
of ipi timeouts.
Discussed with: tmm
|
|
|
|
|
|
|
|
|
|
| |
mutexes are supposed to only be used as leaf mutexes, and what appear
to be separate pool mutexes could be aliased together, it is bad idea
for a thread to attempt to hold two pool mutexes at the same time.
Slightly rearrange the code in kern_open() so that FILE_UNLOCK() is
called before calling VOP_GETVOBJECT(), which will grab the v_vnlock
mutex.
|
|
|
|
|
|
|
|
| |
reporting who did it.
Also, fix a style bug introduced in the previous change.
MFC after: 1 week
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
drivers that implemnt the i2c bit banging bus interface not have to
recompile iicbb in order to add an attachment for it.
This will mean the bktr and other definitions can go back to their
respective drivers.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Mark that it cannot handle greater than 4GB of RAM at this time. Fixing
that will come later. Fail any attempts to dump above thati limit.
- If a call to aac_disk_dump() needs to be split into multiple i/o's,
increment the virtual offset after each i/o instead of just dumping the
same offset over and over again.
- Bail out if bus_dmamap_load() returns an error. Error recovery is likely
not possible.
|
|
|
|
|
|
| |
used by the zero-copy sockets implementation.
Reviewed by: gallatin
|
|
|
|
|
|
|
| |
expects one to use. Only the functions used by XFree86 are actually
implemented.
Glanced at by: tmm
|
|
|
|
| |
rather than assume that only DTYPE_VNODE is seekable.
|
|
|
|
|
|
|
|
|
| |
systems to fail more gracefully when a file descriptor exhaustion situation
occurs.
Original patch by: David G. Andersen <dga@lcs.mit.edu>
PR: 45353
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
the values that are "reserved", but they are not reserved anywhere else
so I'm assuming this is what they were unreserved for. Unfortunately
some of the values for local syscons types overlap the values used for
sbus adapters elsewhere, so we can't have all the same values.
|