| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
Submitted by: Chris Dionissopoulos, Theo Schlossnagle
PR: kern/78681
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a serial console anyway because input-device is set to keyboard and
output-device is set to screen but no keyboard is plugged in don't
assume that a device node for the input-device alias exists. While
this is true for RS232 keyboards (the node of the SCC and UART
respectively which controls the keyboard doesn't disappear when no
keyboard is plugged in) this assumption breaks for USB keyboards.
It's most likely also not true for PS/2 keyboards but OFW doesn't
reliably switch to a serial console when the potential keyboard is
a PS/2 one which isn't plugged in so this couldn't be verified
properly.
Reported by: Will Andrews <will@csociety.org>, obrien
MFC after: 1 week
|
|
|
|
|
| |
Reviewed by: rwatson
MFC after: 1 week
|
|
|
|
|
| |
Reviewed by: rwatson
MFC after: 1 week
|
|
|
|
|
|
| |
so that the socket lock is held over the test-and-set removal of the
accept filter option during connect, and the two socket mutex regions
(transition to connected, perform accept filter) are combined.
|
|
|
|
|
|
| |
suppress logging of interface link state changes.
Requested by: sam, kan
|
|
|
|
|
|
|
| |
from uipc_socket.c to uipc_accf.c in do_getopt_accept_filter(), so that it
now matches do_setopt_accept_filter(). Slightly reformulate the logic to
match the optimistic allocation of storage for the argument in advance,
and slightly expand the coverage of the socket lock.
|
|
|
|
| |
and do exactly what last commit message described.
|
|
|
|
|
| |
allocation up front before grabbing the socket mutex and doing the
registration work. The result is a lot cleaner.
|
|
|
|
|
|
| |
- Bump copyright year.
MFC after: 3 days
|
| |
|
| |
|
| |
|
|
|
|
| |
consumed.
|
|
|
|
|
|
|
| |
available RAM. This also results in the global bounce page limit being
applied to zones instead of globally.
Submitted by: Petr Lampa (in part)
|
|
|
|
|
| |
Submitted by: FUJITA Kazutoshi <fujita at soum dot co dot jp>
Reviewed by: sam (mentor)
|
|
|
|
|
| |
Submitted by: Joerg Sonnenberger <joerg@britannica.bec.de>
Obtained from: OpenBSD (commited fix to PR 3455)
|
|
|
|
| |
Submitted by: jmallett
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
OR the physical address with alpha_XXX_dmamap_or to get the DMA address,
like the name of the variable suggests. However, while we were doing
this correctly in the alpha_XXX_dmamap() macro, the busdma code added
the variable to the physical address instead of or'ing it. Fortunately
and if my math is not entirely wrong, you would need more than 128GB of
RAM and a device able to do DMA in 64bits to experience the bug.
Spotted by: cognet
|
|
|
|
|
|
|
| |
Demanded by: DES
Encouraged by: scottl
Obtained from: q@onthenet.com.au (partially)
KNF'ed by: obrien
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
|
|
|
|
| |
Demanded by: DES
Encouraged by: scottl
|
|
|
|
| |
simpler one.
|
| |
|
|
|
|
| |
nul-terminate the dp->d_name directly and only copy the string.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
long filename. Each substring is indexed by the windows ID, a
sequential one-based value. The previous code was extremely slow,
doing a malloc/strcpy/free for each substring.
This code optimizes these routines with this in mind, using the ID
to index into a single array and concatenating each WIN_CHARS chunk
at once. (The last chunk is variable-length.)
This code has been tested as working on an FS with difficult filename
sizes (255, 13, 26, etc.) It gives a 77.1% decrease in profiled
time (total across all functions) and a 73.7% decrease in wall time.
Test was "ls -laR > /dev/null".
Per-function time savings:
mbnambuf_init: -90.7%
mbnambuf_write: -18.7%
mbnambuf_flush: -67.1%
MFC after: 1 month
|
|
|
|
|
| |
This changes things like whitespace, inconsistent use of #ifndef vs
#if !defined(), different macro argument orders, mismatched comments, etc.
|
| |
|
|
|
|
| |
on amd64, I'm removing them here)
|
|
|
|
| |
Reported by: phk
|
| |
|
| |
|
| |
|
|
|
|
|
| |
post-SMPng world order. Centralize handling of the socket option
clear case in do_setopt_accept_filter().
|
|
|
|
|
| |
default rate control algorithm; this should be done differently but for
now use this simple solution
|
|
|
|
| |
lock.
|
|
|
|
| |
(I forgot to commit this in my previous commit)
|
|
|
|
|
|
| |
the two became almost identical since latest KAME merge.
Discussed with: sam
|
|
|
|
|
|
|
|
|
|
| |
socket lock around knlist_init(), so don't.
Hard code the setting of the socket reference count to 1 rather than
using soref() to avoid asserting the socket lock, since we've not yet
exposed the socket to other threads.
This removes two mutex operations from each socket allocation.
|
|
|
|
| |
like this at some point, but for now it clutters the source.
|
| |
|
|
|
|
|
|
| |
error(ath_hal_computetxtime) during module loading.
Reviewed by: sam (mentor)
|
|
|
|
| |
this is required to integrate opencrypto into crypto.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so that the socket does not generate SIGPIPE, only EPIPE, when a write
is attempted after socket shutdown. When the option was introduced in
2002, this required the logic for determining whether SIGPIPE was
generated to be pushed down from dofilewrite() to the socket layer so
that the socket options could be considered. However, the change in
2002 omitted modification to soo_write() required to add that logic,
resulting in SIGPIPE not being generated even without SO_NOSIGPIPE when
the socket was written to using write() or related generic system calls.
This change adds the EPIPE logic to soo_write(), generating a SIGPIPE
signal to the process associated with the passed uio in the event that
the SO_NOSIGPIPE option is not set.
Notes:
- The are upsides and downsides to placing this logic in the socket
layer as opposed to the file descriptor layer. This is really fd
layer logic, but because we need so_options, we have a choice of
layering violations and pick this one.
- SIGPIPE possibly should be delivered to the thread performing the
write, not the process performing the write.
- uio->uio_td and the td argument to soo_write() might potentially
differ; we use the thread in the uio argument.
- The "sigpipe" regression test in src/tools/regression/sockets/sigpipe
tests for the bug.
Submitted by: Mikko Tyolajarvi <mbsd at pacbell dot net>
Talked with: glebius, alfred
PR: 78478
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
| |
and inlining the small printing utility functions.
Create a function that can be used to produce printable representations
of flag words.
|
| |
|
|
|
|
|
| |
with leading underscore followed by an uppercase letter are in the
implementation namespace.
|