| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
served no purpose.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove the initialization of PQ_NONE's cnt and lcnt. They aren't
used.
vm_page_insert:
Remove an unnecessary dereference.
vm_page_wire:
Remove the one and only (and thus pointless) reference
to PQ_NONE's lcnt.
|
|
|
|
| |
Submitted by: dillon
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I did some tcpdumping the other day and noticed that GETATTR calls
were frequently followed by an ACCESS call to the same file. The
attached patch changes nfs_getattr to fill the access cache as a side
effect. This is accomplished by calling ACCESS rather than
GETATTR. This implies a modest overhead of 4 bytes in the request and
8 bytes in the response compared to doing a vanilla GETATTR.
...
[The patch comprises two parts] The first
is the "real" patch, the second counts misses and hits rather than
fills and hits. The difference is subtle but important because both
nfs_getattr and nfs_access now fill the cache. It also changes the
default value of nfsaccess_cache_timeout to better match the attribute
cache. IMHO, file timestamps change much more frequently than
protection bits.
Submitted by: Bjoern Groenvall <bg@sics.se>
Reviewed by: dillon (partially)
|
|
|
|
|
|
| |
specify a DEVICE_SHUTDOWN method instead.
Reviewed by: me, since nobody else seems to run this hardware in -CURRENT
|
|
|
|
|
|
| |
(which is more like the old than I thought).
Requested-by: imp
|
|
|
|
|
|
| |
during device announcement. (irq, ioport, maddr)
Reviewed by: dfr, peter
|
|
|
|
| |
svr4_sys_sendto() which probably shouldn't have been 'const'.
|
|
|
|
|
|
| |
related to the commit for rev 1.3 of svr4_stat.c.
svr4_sysvec.c also received a copyright message (which is why it grew by
28 lines).
|
|
|
|
|
| |
BSD sockets don't. Guess at a correct emulation for those values (it seems
to work for telnet, ftp and friends)
|
| |
|
|
|
|
| |
Clean-up some unused (or to-be-used) variables in svr4_getcontext()
|
|
|
|
| |
Trust me, this stuff will be in a real manpage before 4.0 ships :-)
|
| |
|
| |
|
|
|
|
|
|
|
| |
their svr4_stat64 structures with old dev_t values instead of udev_t's.
Panic was caused when major() and minor() were called with args which
weren't pointers. The panic was probably introduced in rev 1.51 of
kern_conf.c
|
|
|
|
| |
at boot
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: N. Dudorov <nnd@mail.nsk.ru>
|
|
|
|
| |
parts of the kernel but was not updated in nfs_readdirplusrpc().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
vnodes are locked and never unlocked, which leads to processes starting
to wedge up after doing a mount -o nfsv3,tcp,rdirplus foo:/fs /fs; ls /fs.
The second is that sometimes cnp is accessed without having been
properly initialized: cnp->cn_nameptr points to an earlier name while
"len" contains the length of a current name of different size. This
leads to an attempt to dereference *(cn->cn_nameptr + len) which will
sometimes cause a page fault and a panic.
With these two fixes, client side readdirplus works correctly with
FreeBSD, IRIX 6.5.4 and Solaris 2.5.1 and 2.6 servers.
Submitted by: Matthew Dillon <dillon@backplane.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
being incremented by 4 bytes too few each time through the loop, which
allows more data into the mbuf chain that we really want. In the worst
case, when we're using 32K read/write sizes with a TCP client, this causes
readdirplus replies to sometimes exceed NFS_MAXPACKET which leads to a
panic. This problem cropped up for me using an IRIX 6.5.4 NFSv3 TCP client
with 32K read/write sizes, however supposedly it can be triggered by
WinNT NFS servers too. In theory, it can probably be triggered by any
NFS v3 implementation using TCP as long as it's using the maxiumum block
size.
Reviewed by: Matthew Dillon <dillon@backplane.com>
|
|
|
|
| |
with a graphics head to panic on boot
|
|
|
|
|
| |
previous major update. Bring new code into style alignment with the
existing code. No functional changes.
|
|
|
|
| |
uses (sc->bios.r.eax >> 8) & 0xff instead.
|
|
|
|
| |
Submitted by: Dan Nelson <dnelson@emsphone.com>
|
|
|
|
|
|
|
|
|
| |
space of PCI devices that don't exist cause PCI master & target aborts
rather than returning ~0 or giving a machine check. Bring in some code
from NetBSD to handle this properly.
obtained from: NetBSD
reviewed by: dfr
|
|
|
|
| |
by the fix in rev 1.120, which i wasn't immediately aware of.
|
| |
|
|
|
|
| |
without -O.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Back out a few lines that I haven't dealt with properly yet.
Snickered at by: Mike Smith
|
|
|
|
|
|
|
|
|
| |
- Add support for calling 32-bit code in other segments
- Add support for calling 16-bit protected mode code
Update APM to use this facility.
Submitted by: jlemon
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- device_print_child() either lets the BUS_PRINT_CHILD
method produce the entire device announcement message or
it prints "foo0: not found\n"
Alter sys/kern/subr_bus.c:bus_generic_print_child() to take on
the previous behavior of device_print_child() (printing the
"foo0: <FooDevice 1.1>" bit of the announce message.)
Provide bus_print_child_header() and bus_print_child_footer()
to actually print the output for bus_generic_print_child().
These functions should be used whenever possible (unless you can
just use bus_generic_print_child())
The BUS_PRINT_CHILD method now returns int instead of void.
Modify everything else that defines or uses a BUS_PRINT_CHILD
method to comply with the above changes.
- Devices are 'on' a bus, not 'at' it.
- If a custom BUS_PRINT_CHILD method does the same thing
as bus_generic_print_child(), use bus_generic_print_child()
- Use device_get_nameunit() instead of both
device_get_name() and device_get_unit()
- All BUS_PRINT_CHILD methods return the number of
characters output.
Reviewed by: dfr, peter
|
| |
|
| |
|
| |
|
|
|
|
|
| |
PR: docs/11955
Submitted by: Christian Weisgerber <naddy@mips.rhein-neckar.de>
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
|
|
|
|
|
|
|
|
|
|
|
| |
result of a joined effort with parts contributed by Doug Rabson, Warner
Losh and Stefan Esser (hope I did not forget anybody). Part of the sources
is obtained from NetBSD with modifications.
This code is work in progress:
As of the time of the initial import, a loader.exe executable is built,
which can be loaded on an Alpha with NT only firmware, but no attempt is
made to switch to OSF PAL code as required to start an actual kernel.
|
|
|
|
|
|
|
|
|
|
|
| |
active or not. The only sane thing we can do here is assume that if
APM is supported it might be active at some point, and bail.
In reality, even this isn't good enough; regardless of whether we support
APM or not, the system may well futz with the CPU's clock speed and throw
the TSC off. We need to stop using it for timekeeping except under
controlled circumstances. Curse the lack of a dependable high-resolution
timer.
|
|
|
|
| |
mode initialiser for a while now, and it's looking happy.
|
| |
|