| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
(TNT2 from me)
PR: 12094
Submitted by: Ilya Naumov camel@avias.com
|
|
|
|
| |
kernel virtual address space for UPAGES.
|
|
|
|
|
|
| |
create a nofault entry. It will be used to allocate kmem for upages.
(I am not too happy with all this, but it's better than nothing).
|
|
|
|
|
|
|
|
| |
correctly.
This should fix the "pmap_changebit didn't" panic that some people see.
Reviewed by: dfr
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- this causes POSIX locking to use the thread group leader
(p->p_leader) as the locking thread for all advisory locks.
In non-kernel-threaded code p->p_leader == p, so this will have
no effect.
This results in (more) correct POSIX threaded flock-ing semantics.
It also prevents the leader from exiting before any of the children.
(so that p->p_leader will never be stale) in exit1().
We have been running this patch for over a month now in our lab
under load and at customer sites.
Submitted by: John Plevyak <jplevyak@inktomi.com>
|
|
|
|
|
|
| |
Other brucification tweaks.
Obtained from: bde@freebsd.org
|
|
|
|
| |
here and keep people from building new kernels. :)
|
|
|
|
|
| |
instead of frobbing the buffer access path registers directly. Saves a
few lines of duplicated code.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This means that the driver will add/delete routes when it knows it is
up/down, rather than have the generic code belive it is up if configured.
This is probably most useful for serial lines, although many PHY chips
could probably tell us if we're connected to the cable/hub as well.
|
|
|
|
|
| |
reentrant because it returns a static buffer. This results in a race condition
when/if an interrupt handler calls log(), printf() etc. Fix this.
|
|
|
|
|
|
|
| |
Insure that device mappings get MAP_PREFAULT(_PARTIAL) set,
so that 4M page mappings are used when possible.
Reviewed by: Luoqi Chen <luoqi@watermarkgroup.com>
|
|
|
|
| |
PR: kern/11948
|
| |
|
|
|
|
| |
* Port the fd driver to alpha.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
txdr_hyper and fxdr_hyper tweaks to avoid excessive CPU order knowledge.
nfs_serv.c: don't call nfsm_adj() with negative values, windows clients
could crash servers when doing a readdir of a large directory.
nfs_socket.c: Use IP_PORTRANGE to get a priviliged port without a spin
loop trying to bind(). Don't clobber a mbuf pointer or we get panics
on a NFS3ERR_JUKEBOX error from a server when reusing a freed mbuf.
nfs_subs.c: Don't loose st_blocks on NFSv2 mounts when > 2GB.
Obtained from: OpenBSD
|
|
|
|
| |
Obtained from: OpenBSD (csapuntz)
|
|
|
|
|
|
| |
interrupted write.
Obtained from: fvdl@NetBSD.org via OpenBSD.
|
|
|
|
| |
Submitted by: Matthew Dillon <dillon@apollo.backplane.com> and myself
|
|
|
|
|
|
|
|
|
|
| |
corresponding variable `rc_wakeup_started' in rev.1.36 but broken
again in rev.1.37. This bug only caused excessive polling (it gave
NRC activations for each of the SWI handler and the timeout handler
instead of 1 of each).
Moved cdevsw attachment from the driver probe routine to the driver
attach routine.
|
|
|
|
|
|
| |
fixed half the problem.
Tested by: Michael Scott Boers <mboers@datacompusa.com>
|
|
|
|
|
| |
(It was accidentally added to the BSDI bktr_probe and not the
FreeBSD bktr_probe)
|
|
|
|
|
|
| |
from. 0x50 == 'P' for protoype.
Obtained from: Pat LaVarre <LAVARRE@iomega.com> on linux-usb@suse.com
|
| |
|
|
|
|
| |
Pointed out by: Nobuyuki Koganemaru <kogane@koganemaru.co.jp>
|
|
|
|
|
|
|
|
|
|
|
| |
flag to the kernel to mount a CDROM as the root filesystem. Alternatively,
the boot_cdrom env var can be set.
As Mike Smith noted, "-C is the "wrong" way to do this", but this is
an acceptable stopgap in lieu of a better way.
PR: bin/11884
Reviewed by: msmith@freebsd.org
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to either enqueue or free their mbuf chains, but tcp_usr_send() was
dropping them on the floor if the tcpcb/inpcb has been torn down in the
middle of a send/write attempt. This has been responsible for a wide
variety of mbuf leak patterns, ranging from slow gradual leakage to rather
rapid exhaustion. This has been a problem since before 2.2 was branched
and appears to have been fixed in rev 1.16 and lost in 1.23/1.28.
Thanks to Jayanth Vijayaraghavan <jayanth@yahoo-inc.com> for checking
(extensively) into this on a live production 2.2.x system and that it
was the actual cause of the leak and looks like it fixes it. The machine
in question was loosing (from memory) about 150 mbufs per hour under
load and a change similar to this stopped it. (Don't blame Jayanth
for this patch though)
An alternative approach to this would be to recheck SS_CANTSENDMORE etc
inside the splnet() right before calling pru_send() after all the potential
sleeps, interrupts and delays have happened. However, this would mean
exposing knowledge of the tcp stack's reset handling and removal of the
pcb to the generic code. There are other things that call pru_send()
directly though.
Problem originally noted by: John Plevyak <jplevyak@inktomi.com>
|
| |
|
| |
|
|
|
|
| |
the isa probe has gone hunting for a card on it's own.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
New function getmemsize_pc98 is added in this commit, since PC98 is
quite different in obtaining memory size from IBM-PC. Many lines of
this function is shareable with IBM-PC's getmemsize function, but
sharing needs many #ifdef PC98 statements. Therefore, I gave up
sharing code with IBM-PC's and just added new function.
|
|
|
|
| |
and 1.115, respectively.
|
|
|
|
| |
for the sign bit for roller movement!
|
|
|
|
| |
Pointed out by: Akio Morita <amorita@meadow.scphys.kyoto-u.ac.jp>
|
|
|
|
| |
that actually compiles, and I use it for i386's with 64 bit longs.
|
|
|
|
| |
Submitted by: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
|
|
|
|
| |
Preferred by: phk (rather than committing the patch without review).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
happens if you have a BIOS with a 'Plug & Play OS' setting and you leave
it set to 'Yes.' This is wrong for FreeBSD (and LoseNT): it should be set
to 'No.' Apparently it's still possible to map the iobase of the NIC and
have the card work by reading the config space manually (which is what
the driver does if pci_map_port() fails) but we need to warn the user to
do fix their machine anyway. Anyway, warn the user to check the 'Plug &
Play OS' setting in their BIOS if mapping the io space fails.
|
|
|
|
| |
function for now, but that will change.
|
|
|
|
|
|
|
| |
the BIOS calls to determine the memory configuration. This should fix
problems with >64M for good.
Reviewed by: Mike Smith
|