| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Requested by: n_hibma
Obtained from: NetBSD (original version)
|
|
|
|
|
| |
- Set dow = -1 in mk48txx_gettime() because some drivers (for example
the NetBSD and OpenBSD mk48txx(4)) don't set it correctly.
|
|
|
|
| |
Obtained from: NetBSD
|
| |
|
|
|
|
| |
Submitted by: Maxim Dounin <mdounin@mdounin.ru>
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
This is necessary in order to enable NFSv4 ACL support. The
argument to nfsvno_accchk() was changed to an accmode_t and
the function nfsrv_aclaccess() was no longer needed and,
therefore, deleted.
Reviewed by: trasz
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
Reset the exception handler in the child to main's.
This avoids inappropriate double cleanups or shell duplication when the
exception is caught, such as 'fc' and future 'command eval' and 'command .'.
|
|
|
|
|
| |
Right now the code uses UT_NAMESIZE, but this makes little sense,
because rwho(1) parses files generated by rwhod(8). Not utmp(5) files.
|
|
|
|
|
|
|
| |
An older version of the code used a structure on the stack, instead of a
pointer to the structure. It looks like I didn't adjust the parameters
of the write(2) call, causing the first four/eight bytes of the entry to
be corrupted, instead of writing the entire entry to disk.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
if we end up having to generate one.
PR: kern/133239
Discussed with: yongari
Approved by: ed (mentor)
MFC after: 2 weeks
|
|
|
|
|
| |
Approved by: ed (mentor)
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
to an entry of 'acl', all ACL entries starting with entry_d would be deleted.
Reviewed by: trasz
Approved by: emax (mentor)
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
| |
That is, do not do tilde expansion if any of the CTL* bytes (\201-\210), not
only CTLESC and CTLQUOTEMARK, are encountered. Such an expansion would look
up a user name with sh's internal representation.
The parser does not currently distinguish between backslashed and
unbackslashed \201-\210, so tilde expansion of user names with these bytes
in them is not so easy to fix.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so requests may bubble up to a host-PCI bridge driver.
- Distinguish between PCI and PCIe bridges in the device description
so it's a bit easier to follow what hangs off of what in the dmesg.
Unfortunately we can't also tell PCI and PCI-X apart based on the
information provided in the OFW device tree.
- Add quirk handling for the ALi M5249 found in Fire-based machines
which are used as a PCIe-PCIe bridge there. These are obviously
subtractive decoding as as they have a PCI-ISA bridge on their
secondary side (and likewise don't include the ISA I/O range in
their bridge decode) but don't indicate this via the class code.
Given that this quirk isn't likely to apply to all ALi M5249 and
I have no datasheet for these chips so I could implement a check
using the chip specific bits enabling subtractive decoding this
quirk handling is added to the MD code rather than the MI one.
|
|
|
|
|
| |
Because strings are null terminated now, there is no need to copy
ut_line into a separate buffer first. Also enable WARNS.
|
| |
|
|
|
|
|
|
| |
commands.
MFC after: 1 month
|
| |
|
|
|
|
| |
The maximum user login length should have nothing to do with <utmp.h>.
|
| |
|
|
|
|
| |
MFC after: 3 days
|
| |
|
| |
|
|
|
|
| |
make file systems optimally aligned and tuned for better performance.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
dev.ste.%d.int_rx_mod.
While I'm here add .Xr vlan as ste(4) supports long frames.
|
|
|
|
|
| |
Most of this is adding const keywords, but setvar() in var.c had to be
changed somewhat more.
|
|
|
|
| |
While I'm here simplify SIOCSIFCAP handler.
|
|
|
|
|
| |
Because strings are guaranteed to be null terminated, there is no need
for excessive copying of strings, such as the line name.
|
|
|
|
| |
Approved by: harti
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unlike TX interrupt, ST201 does not provide any mechanism to
suppress RX interrupts. ste(4) can generate more than 70k RX
interrupts under heavy RX traffics such that these excessive
interrupts make system useless to process other useful things.
Maybe this was the major reason why polling support code was
introduced to ste(4).
The STE_COUNTDOWN register provides a programmable counter that
will generate an interrupt upon its expiration. We program
STE_DMACTL register to use 3.2us clock rate to drive the counter
register. Whenever ste(4) serves RX interrupt, the driver rearm
the timer to expire after STE_IM_RX_TIMER_DEFAULT time and disables
further generation of RX interrupts. This trick seems to work well
and ste(4) generates less than 8k RX interrupts even under 64 bytes
UDP torture test. Combined with TX interrupts, the total number of
interrupts are less than 10k which looks reasonable on heavily
loaded controller.
The default RX interrupt moderation time is 150us. Users can change
the value at any time with dev.ste.%d.int_rx_mod sysctl node.
Setting it 0 effectively disables the RX interrupt moderation
feature. Now we have both TX/RX interrupt moderation code so remove
loop of interrupt handler which resulted in sub-optimal performance
as well as more register accesses.
|
|
|
|
| |
Implement support for interrupt descriptions.
|
| |
|
|
|
|
| |
like the other architectures do.
|
|
|
|
|
| |
NetBSD rev 1.19.
- Make the functions match their prototypes regarding static.
|
|
|
|
|
|
| |
M5229 appears to be once again fixed. If this happens to return
we probably should disable ATAPI DMA in ataacerlabs(4) instead
just like the Linux libATA does.
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is already done by evalcommand(), unless special-ness has been removed,
in which case variable assignments should not persist. (These are currently
always special builtins, but this will change later: command builtin,
command substitution.)
This also fixes a memory leak when calling . with variable assignments.
Example:
valgrind --leak-check=full sh -c 'x=1 . /dev/null; x=2'
|
|
|
|
| |
hoping that rest will fit.
|
|
|
|
| |
are missing from NOTES files.
|
|
|
|
|
| |
underlying provider's stripe, multiplied by number of data disks in array,
due to transformation done, as array stripe.
|
|
|
|
|
|
|
|
|
|
|
| |
in intr_execute_handlers(). If we managed to get here without an
associated interrupt controller we have way bigger problems.
While at it predict stray vector interrupts as false as they are
rather unlikely.
- Don't blindly call the clear function of an interrupt controller
when adding a handler in inthand_add() as interrupt controllers
like the one driven by upa(4) are auto-clearing and thus provide
NULL instead.
|
|
|
|
| |
components, hoping others fit, if they are not equal.
|
|
|
|
| |
stripe (optimal access block) size and offset.
|
| |
|