| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Reviewed by: bde
Approved by: sheldonh (mentor)
|
|
|
|
| |
assertion in setrunqueue() fails.
|
|
|
|
| |
Approved in concept a long time ago by: msmith
|
| |
|
| |
|
|
|
|
| |
gathering is not an x86 cpu feature)
|
|
|
|
| |
compiled this stuff if NBKTR was zero.
|
| |
|
| |
|
| |
|
|
|
|
| |
the ifdef completely.
|
| |
|
| |
|
|
|
|
| |
be needed, but this seems sane on my laptop.
|
|
|
|
| |
and FreeBSD 3.
|
|
|
|
|
|
| |
zero it.
Reviewed by: dfr, peter
|
| |
|
|
|
|
|
|
|
| |
At hz values of 1000 and above the overflows caused net.inet.tcp.keepidle
to be reported as negative.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
data structures pick up security and synchronization primitives, it
becomes increasingly desirable not to arbitrarily export them via
include files to userland, as the userland applications pick up new
#include dependencies.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
|
|
|
|
|
|
| |
failing because of the error.
Obtained from: TrustedBSD Project
Sponsored by: DARPA, NAI Labs
|
|
|
|
|
|
|
|
|
|
| |
windows. Right now we only support pci chips that are memory mapped.
These are the most common bridges in use today and will help a large
majority of the users.
I/O mapped PCI chips support this functionality in a different way, as
do some of the ISA bridges (but only when mounted on a motherboard).
These chips are not supported by this change.
|
|
|
|
|
| |
in kern/vfs_bio.c are already locked.)
o Assert that the page queues lock is held in vm_page_try_to_cache().
|
| |
|
|
|
|
|
| |
vm_pageout_scan(). (The others are already locked.)
o Assert that the page queues lock is held in vm_page_cache().
|
| |
|
|
|
|
| |
vm_pageout_page_stats().
|
| |
|
|
|
|
|
| |
still for the IPI vectors, but 63 isn't enough. There is an fxp at IRQ 86
on the Itanium2 box I have.
|
|
|
|
| |
o Micro-optimize the control flow in vm_contig_launder().
|
| |
|
|
|
|
| |
Forgotten by: mckusick
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug#1: The GetStatus() function returns radically different pointers that
do not match any packets we transmitted. I think it might be pointing to
a copy of the packet or something. Since we do not transmit more than
one packet at a time, just wait for "anything".
Bug#2: The Receive() function takes a pointer and a length. However, it
either ignores the length or otherwise does bad things and writes outside
of ptr[0] through ptr[len-1]. This is bad and causes massive stack
corruption for us since we are receiving packets into small buffers on
the stack. Instead, Receive() into a large enough buffer and bcopy the
data to the requested area.
|
|
|
|
|
| |
box that I have. We have no EFI disk drivers yet anyway (maybe that is the
problem).
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
handler in the kernel at the same time. Also, allow for the
exec_new_vmspace() code to build a different sized vmspace depending on
the executable environment. This is a big help for execing i386 binaries
on ia64. The ELF exec code grows the ability to map partial pages when
there is a page size difference, eg: emulating 4K pages on 8K or 16K
hardware pages.
Flesh out the i386 emulation support for ia64. At this point, the only
binary that I know of that fails is cvsup, because the cvsup runtime
tries to execute code in pages not marked executable.
Obtained from: dfr (mostly, many tweaks from me).
|
|
|
|
| |
ffs_softdep.c:1630: warning: int format, different type arg (arg 2)
|
|
|
|
| |
Sponsored by: The Weather Channel
|
|
|
|
| |
Sponsored by: The Weather Channel
|
|
|
|
|
|
| |
the loadav. This is not real load. If you have a nice process running in
the background, pagezero may sit in the run queue for ages and add one to
the loadav, and thereby affecting other scheduling decisions.
|
| |
|
|
|
|
|
|
|
|
| |
chipset used for P4-Xeon machines
PR: kern/38894
Tested-by: "Marc G. Fournier" <scrappy@hub.org>
Submitted-by: Mark Tinguely (partially)
|
|
|
|
| |
unnecessary retransmissions.
|
| |
|
|
|
|
|
|
|
|
| |
- Sanity check the mount options list (remove duplicates) with
vfs_sanitizeopts().
- Fix some malloc(0)/free(NULL) bugs.
Reviewed by: rwatson (some time ago)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As this code is not actually used by any of the existing
interfaces, it seems unlikely to break anything (famous
last words).
The internal kernel interface to manipulate these attributes
is invoked using two new IO_ flags: IO_NORMAL and IO_EXT.
These flags may be specified in the ioflags word of VOP_READ,
VOP_WRITE, and VOP_TRUNCATE. Specifying IO_NORMAL means that
you want to do I/O to the normal data part of the file and
IO_EXT means that you want to do I/O to the extended attributes
part of the file. IO_NORMAL and IO_EXT are mutually exclusive
for VOP_READ and VOP_WRITE, but may be specified individually
or together in the case of VOP_TRUNCATE. For example, when
removing a file, VOP_TRUNCATE is called with both IO_NORMAL
and IO_EXT set. For backward compatibility, if neither IO_NORMAL
nor IO_EXT is set, then IO_NORMAL is assumed.
Note that the BA_ and IO_ flags have been `merged' so that they
may both be used in the same flags word. This merger is possible
by assigning the IO_ flags to the low sixteen bits and the BA_
flags the high sixteen bits. This works because the high sixteen
bits of the IO_ word is reserved for read-ahead and help with
write clustering so will never be used for flags. This merge
lets us get away from code of the form:
if (ioflags & IO_SYNC)
flags |= BA_SYNC;
For the future, I have considered adding a new field to the
vattr structure, va_extsize. This addition could then be
exported through the stat structure to allow applications to
find out the size of the extended attribute storage and also
would provide a more standard interface for truncating them
(via VOP_SETATTR rather than VOP_TRUNCATE).
I am also contemplating adding a pathconf parameter (for
concreteness, lets call it _PC_MAX_EXTSIZE) which would
let an application determine the maximum size of the extended
atribute storage.
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
| |
when VM_ALLOC_WIRED is specified: set the PG_MAPPED bit in flags.
o In both vm_page_wire() and vm_page_allocate() add a comment saying
that setting PG_MAPPED does not belong there.
|