| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Obtained from: pluknet
MFC after: 1 week
|
| |
|
|
|
|
| |
vm_pageout_object_deactivate_pages().
|
|
|
|
|
|
|
| |
cleverness by vm_fault() to avoid repeatedly releasing and reacquiring the
page queues lock pointless.
Reviewed by: kib, kmacy
|
|
|
|
|
|
|
|
|
| |
HAL/Fujitsu) CPUs. For the most part this consists of fleshing out the
MMU and cache handling, it doesn't add pmap optimizations possible with
these CPU, yet, though.
With these changes FreeBSD runs stable on Fujitsu Siemens PRIMEPOWER 250
and likely also other models based on SPARC64 V like 450, 650 and 850.
Thanks go to Michael Moll for providing access to a PRIMEPOWER 250.
|
|
|
|
|
|
| |
driver for CAM ATA subsystem. This driver supports same hardware as
atamarvell, ataadaptec and atamvsata drivers from ata(4), but provides
many additional features, such as NCQ, PMP, etc.
|
|
|
|
| |
Reviewed by: alc
|
|
|
|
| |
Reviewed by: kib
|
|
|
|
| |
Approved by: marcel
|
|
|
|
| |
Approved by: marcel
|
|
|
|
| |
held.
|
|
|
|
|
|
|
|
|
|
| |
to unconditionally set PG_REFERENCED on a page before sleeping. In many
cases, it's perfectly ok for the page to disappear, i.e., be reclaimed by
the page daemon, before the caller to vm_page_sleep() is reawakened.
Instead, we now explicitly set PG_REFERENCED in those cases where having
the page persist until the caller is awakened is clearly desirable. Note,
however, that setting PG_REFERENCED on the page is still only a hint,
and not a guarantee that the page should persist.
|
|
|
|
|
|
|
|
|
|
| |
revision, r207450, to this file. Specifically, between dropping the page
queues lock in vm_contig_launder() and reacquiring it in
vm_contig_launder_page(), the page may be removed from the active or
inactive queue. It could be wired, freed, cached, etc. None of which
vm_contig_launder_page() is prepared for.
Reviewed by: kib, kmacy
|
| |
|
|
|
|
| |
first data word.
|
|
|
|
|
|
|
| |
- device initiated power management (some devices support only this way);
- Automatic Partial to Slumber Transition (more power saving);
- DMA auto-activation (expected to slightly improve performance).
More features could be added later, when hardware supports.
|
| |
|
|
|
|
|
|
|
| |
usual operation, but required in some conditions to make queue running
after being shrinked.
MFC after: 3 days
|
|
|
|
|
|
|
| |
specified to vm_map_find(), then retry the vm_map_findspace() if
vm_map_insert() fails because the aligned space is already partly used.
Reported by: Neel Natu
|
|
|
|
|
|
|
|
|
|
| |
Spaces and various other characters in pathnames are not passed through
literally by xargs in its default mode. Instead, use find . -exec ... {} +
Although the -- argument is not strictly required here, add it anyway to
avoid surprises when modifying the code to find -f -somedir ...
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
process mappings for that PMC. Nothing ever reads pmc logs out of a counting PMC, so the log buffers were leaked when the PMC was deconfigured. The process mappings are only useful for sampling PMCs anyway, so only log the mappings if the PMC is a sampling PMC.
This bug would cause allocating sample-mode PMCs to fail with ENOMEM after allocating several counting-mode PMCs.
Approved by: jkoshy (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
This option checks for empty pathnames and components starting with '-'.
Our -p option also checks for the latter, which remains the case.
MFC after: 1 week
|
|
|
|
|
|
|
| |
cachestate qualifier on the Atom processor. Other Intel processors do not accept a cachestate qualifier and currently hwpmc will return EINVAL if you try to use the EXT_SNOOP event on those processors
Approved by: jkoshy (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
This tunable improves fine-tuning of ZFS write throttling.
PR: kern/146108
Suggested by: Nikolay Denev <ndenev at gmail.com>
Approved by: pjd, delphij (mentor)
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
understandable.
Approved by: pjd, delphij (mentor)
MFC after: 3 days
|
|
|
|
| |
Submitted by: jeff
|
|
|
|
|
| |
Reviewed by: bz, rwatson
MFC after: 3 days
|
|
|
|
| |
workaround (WAR) is needed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that generates a fatal bus trap. Normally, the chips are setup to do
128 byte DMA bursts, but when on this CPU, they can only safely due
4-byte DMA bursts due to this bug. Details of the exact nature of the
bug are sketchy, but some can be found at
https://forum.openwrt.org/viewtopic.php?pid=70060 on pages 4, 5 and 6.
There's a small performance penalty associated with this workaround,
so it is only enabled when needed on the Atheros AR71xx platforms.
Unfortunately, this condition is impossible to detect at runtime
without MIPS specific ifdefs. Rather than cast an overly-broad net
like Linux/OpenWRT dues (which enables this workaround all the time on
MIPS32 platforms), we put this option in the kernel for just the
affected machines. Sam didn't like this aspect of the patch when he
reviewed it, and I'd love to hear sane proposals on how to fix it :)
Reviewed by: sam@
|
|
|
|
|
|
|
|
| |
function ruxagg_tlock().
Convert the definition of kern_getrusage() to ANSI C.
Submitted by: Alexander Krizhanovsky <ak natsys-lab com>
MFC after: 1 week
|
|
|
|
|
| |
Suggested by: bde
MFC after: 1 week
|
|
|
|
|
|
|
| |
Document -j switch in usage() to reflect recent SUJ work.
Submitted by: Alastair Hogge
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
section holding the config file to sh_addralign bytes using NULs.
This bogusly triggers an assert. Break out of the loop when we hit an
NUL within that many bytes of the end.
MFC after: 3 days
|
|
|
|
|
|
|
| |
- re-assign page queue lock "Q"
- assign page lock "P"
- update several uncommented fields
- observe that hold_count is now protected by the page lock "P"
|
|
|
|
| |
connected to build). The idea/code was shamelessly taken from r207329.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because script(1) now reliably terminates when the TTY is closed, it may
be the case that the call to wait3() occurs just before the child
process exits. This causes error codes to be ignored.
Just change script(1) to use waitpid() instead of wait3(). This makes it
more portable and prevents the need for a loop, since waitpid() only
returns a specified process.
PR: bin/146189
Tested by: amdmi3@, older version
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Reported by: Michael Butler
|
|
|
|
| |
- release page queue lock before calling vm_pageout_flush
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of catching SIGPIPE and jumping out of the signal handler with
longjmp, ignore it and handle write errors to the local output by exiting
from there. I have changed the error message to mention the local output
instead of NetBSD's wrong "Connection closed by foreign host". Write errors
to the network were already handled by exiting immediately and this now
applies to EPIPE too.
The code assumed that SIGPIPE could only be generated by the network
connection; if it was generated by the local output, it would longjmp out of
the signal handler and write an error message which caused another SIGPIPE.
PR: 19773
Obtained from: NetBSD
MFC after: 1 week
|
|
|
|
|
| |
- don't leak the page lock if m->object is NULL
(assuming that that check will in fact even be valid when m->object is protected by the page lock)
|
| |
|
|
|
|
|
| |
Tested by: James LaLagna < jameslalagna <> gmail dot com >
MFC after: 5 days
|
|
|
|
|
| |
Tested by: James LaLagna < jameslalagna <> gmail dot com >
MFC after: 5 days
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
does. Without this change, Yukon Extreme seems to generate lots of
RX FIFO overruns even though controller has available RX buffers.
These excessive RX FIFO overruns generated lots of pause frames
which in turn killed devices plugged into switch. It seems there is
still occasional RX frame corruption on Yukon Extreme but this
change seems to fix the pause frame storm.
Reported by: jhb
Tested by: jhb
MFC after: 5 days
|
|
|
|
|
|
|
| |
physaddr was being used in the macro (1 should be
used not 2)...
Obtained from: JC
|
|
|
|
|
|
|
|
|
|
|
|
| |
taskqueue_drain(9) will not correctly detect whether a task is
currently running. The check is against a field in the taskqueue
struct, but for a threaded queue with more than one thread, multiple
threads can simultaneously be running a task, thus stomping over the
tq_running field.
Submitted by: Matthew Fleming <matthew.fleming@isilon.com>
Reviewed by: jhb
Approved by: dfr (mentor)
|