summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Oops, forgot to commit one file in the fd driver mega update. Here itjoerg2001-12-161-17/+22
| | | | | | is, some more constants for NE765 & Co. Pointed out by: silby, Dave Cornejo <dave@dogwood.com>
* Remove PC98 code. This file is not used by PC98.nyan2001-12-162-34/+0
|
* Add code to export and print the description associated to sysctlluigi2001-12-162-1/+29
| | | | | | | | | | | | | | | | variables. Use the -d flag in sysctl(8) to see this information. Possible extensions to sysctl: + report variables that do not have a description + given a name, report the oid it maps to. Note to developers: have a look at your code, there are a number of variables which do not have a description. Note to developers: do we want this in 4.5 ? It is a very small change and very useful for documentation purposes. Suggested by: Orion Hodson
* Typo.archie2001-12-151-1/+1
|
* Don't free a structure containing a 'struct callout' structure while thatarchie2001-12-151-8/+17
| | | | | | callout is still pending. MFC after: 3 days
* Fix access-after-free bug added in revision 1.31.archie2001-12-151-4/+5
| | | | | Detected by: INVARIANTS MFC after: 2 days
* Long promised major enhancement set for the floppy disk driver:joerg2001-12-155-576/+1020
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | . The main device node now supports automatic density selection for commonly used media densities. So you can stuff your 1.44 MB and 720 KB media into your drive and just access /dev/fd0, no questions asked. It's all that easy, isn't it? :) . Device density handling has been completely overhauled. The old way of hardwired kernel density knowledge is no longer there. Instead, the kernel now implements 16 subdevices per drive. The first subdevice uses automatic density selection, while the remaining 15 devices are freely programmable. They can be assigned an arbitrary name of the form /dev/fd[:digit]+.[:digit:]{1,4}, where the second number is meant to either implement device names that are mnemonic for their raw capacity (as it used to be), or they can alternatively be created as "anonymous" devices like fd0.1 through fd0.15, depending on the taste of the administrator. After creating a subdevice, it is initialized to the maximal native density of the respective drive type, so it needs to be customized for other densities by using fdcontrol(8). Pseudo-partition devices (fd0a through fd0h) are still supported as symlinks. . The old hack to use flags 0x1 to always assume drive 0 were there is no longer supported; this is now supposed to be done by wiring the devices down from the loader via device flags. On IA32 architectures, the first two drives are looked up in the CMOS configuration records though. On PCMCIA (i. e., the Y-E Data controller of the Toshiba Libretto), a single drive is always assumed. . Other specialities like disabling the FIFO and not probing the drive at boot-time are selected by per-controller or per-drive flags, too. . Unit attentions (media has been changed) are supposed to be detected now; density autoselection only occurs after a unit attention. (Can be turned off by a per-drive flag, this will cause each Fdopen() to perform the autoselection.) . FM floppies can be handled now (on controllers that actually support it -- not all do these days). . Fdopen() can be told to avoid density selection by setting O_NONBLOCK; this leaves the descriptor in a half-opened state where only a few ioctls are accepted. This is necessary to run fdformat on a device that uses automatic density selection (since you cannot autoselect on an unformatted medium, obviously). . Just differentiate between a plain old NE765 and the enhanced chips, but don't try more; the existing code was wrong and only misdetected the chips anyway. BUGS and TODOs: . All documentation update still needs to be done. . Formatting not-so-standard format yields unpredictable results; i have yet to figure out why this happens. "Standard" formats like 720 and 1440 KB do work, however. . rc scripts are needed to setup device nodes with nonstandard densities (like the old /dev/fdN.MMM we used to have). . Obtaining device flags from the kernel environment doesn't work yet, thus currently only drives that are present in (IA32) CMOS are really detected. Someone who knows the odds and ends about device flags is needed here, i can't figure out what i'm doing wrong. . 2.88 MB still needs to be done.
* Add modules of scsi_low based SCSI drivers ncv, nsp, stg, and commonnon2001-12-151-0/+4
| | | | | | part scsi_low. Submitted-by: takawata
* Add module directories and makefiles for ncv, nsp, stg and scsi_lownon2001-12-154-0/+38
| | | | | | KLD modules. Submitted-by: takawata
* o Add KLD support for scsi_low.non2001-12-154-0/+14
| | | | | | o Add KLD dependency of ncv, nsp and stg drivers to scsi_low. Submitted by: takawata
* Add support for suspending/resuming CardBus bridges.imp2001-12-153-7/+87
| | | | | | | We really should have and use power state information, but none exists today. Submitted by: YAMAMOTO Shigeru-san <shigeru@iij.ad.jp>
* Patch up some existing style bugs and some that crept in with thepeter2001-12-154-16/+17
| | | | DEVICE_POLLING stuff.
* Fix (again) some blatent style bugs in DEVICE_POLLING code.peter2001-12-151-9/+10
|
* Add support for 56 bit MPPE encryption.archie2001-12-152-9/+12
| | | | MFC after: 3 days
* Fix some nits in fork_exit() so it more properly duplicates the backendjhb2001-12-141-4/+4
| | | | | | | | | of mi_switch: - Set the oncpu value for the current thread. - Always set switchticks, not just in the SMP case. - Add a KTR entry for fork_exit that is the same as the "new proc" entry in mi_switch(). - Release sched_lock a bit later like we do with mi_switch().
* Add description of DEVICE_POLLING option.luigi2001-12-142-0/+38
|
* Clarify the comments related to DUMMYNET and HZluigi2001-12-142-14/+24
| | | | MFC after: 3 days
* Fix two typos, TR6() and ITR6() need to use CTR6(), not CTR5().jhb2001-12-141-2/+2
|
* Make bpf's read timeout feature work more correctly withjdp2001-12-142-6/+60
| | | | | | | | | | | | | | | | | | | | | select/poll, and therefore with pthreads. I doubt there is any way to make this 100% semantically identical to the way it behaves in unthreaded programs with blocking reads, but the solution here should do the right thing for all reasonable usage patterns. The basic idea is to schedule a callout for the read timeout when a select/poll is done. When the callout fires, it ends the select if it is still in progress, or marks the state as "timed out" if the select has already ended for some other reason. Additional logic in bpfread then does the right thing in the case where the timeout has fired. Note, I co-opted the bd_state member of the bpf_d structure. It has been present in the structure since the initial import of 4.4-lite, but as far as I can tell it has never been used. PR: kern/22063 and bin/31649 MFC after: 3 days
* Disabled input hardware checksum due to it being calculated incorrecteddg2001-12-141-0/+2
| | | | | | | | for some packets, in particular small (0 byte payload) packets. May also be related to TCP options. Approved by: wpaul MFC after: 3 days
* Adjust the timings for the SiS chips a bit, also add the SiS 645.sos2001-12-142-13/+17
| | | | Cosmetics on the Acer chips (print right modes)
* Do be so anal on detach, properly free interrupt even if no devices.sos2001-12-141-1/+1
|
* o Add IPOPT_ESO for the 'Extended Security' IP option (RFC1108)rwatson2001-12-141-0/+1
| | | | Obtained from: TrustedBSD Project
* o Add definition for IPOPT_CIPSO, the commercial security IP optionrwatson2001-12-141-0/+1
| | | | | | | number. Submitted by: Ilmar S. Habibulin <ilmar@watson.org> Obtained from: TrustedBSD Project
* whitespace and style fixes recovered from -stable.jlemon2001-12-141-33/+35
|
* minor style and whitespace fixes.jlemon2001-12-141-11/+12
|
* whitespace fixes.jlemon2001-12-146-12/+12
|
* minor whitespace fixes.jlemon2001-12-141-1/+1
|
* minor style fix.jlemon2001-12-142-1/+2
|
* When removing kqueue descriptors from the descriptor table during a fork,jlemon2001-12-141-3/+8
| | | | | | update fd_freefile and fd_lastfile as well, to keep things in sync. Pointed out by: Debbie Chu <dchu@juniper.net>
* Reduce the local network slowstart flightsize from infinity to 4 packets.silby2001-12-141-1/+1
| | | | | | | | | | Now that we've increased the size of our send / receive buffers, bursting an entire window onto the network may cause congestion. As a result, we will slow start beginning with a flightsize of 4 packets. Problem reported by: Thomas Zenker <thz@Lennartz-electronic.de> MFC after: 3 days
* Device Polling code for -current.luigi2001-12-1418-3/+816
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Non-SMP, i386-only, no polling in the idle loop at the moment. To use this code you must compile a kernel with options DEVICE_POLLING and at runtime enable polling with sysctl kern.polling.enable=1 The percentage of CPU reserved to userland can be set with sysctl kern.polling.user_frac=NN (default is 50) while the remainder is used by polling device drivers and netisr's. These are the only two variables that you should need to touch. There are a few more parameters in kern.polling but the default values are adequate for all purposes. See the code in kern_poll.c for more details on them. Polling in the idle loop will be implemented shortly by introducing a kernel thread which does the job. Until then, the amount of CPU dedicated to polling will never exceed (100-user_frac). The equivalent (actually, better) code for -stable is at http://info.iet.unipi.it/~luigi/polling/ and also supports polling in the idle loop. NOTE to Alpha developers: There is really nothing in this code that is i386-specific. If you move the 2 lines supporting the new option from sys/conf/{files,options}.i386 to sys/conf/{files,options} I am pretty sure that this should work on the Alpha as well, just that I do not have a suitable test box to try it. If someone feels like trying it, I would appreciate it. NOTE to other developers: sure some things could be done better, and as always I am open to constructive criticism, which a few of you have already given and I greatly appreciated. However, before proposing radical architectural changes, please take some time to possibly try out this code, or at the very least read the comments in kern_poll.c, especially re. the reason why I am using a soft netisr and cannot (I believe) replace it with a simple timeout. Quick description of files touched by this commit: sys/conf/files.i386 new file kern/kern_poll.c sys/conf/options.i386 new option sys/i386/i386/trap.c poll in trap (disabled by default) sys/kern/kern_clock.c initialization and hardclock hooks. sys/kern/kern_intr.c minor swi_net changes sys/kern/kern_poll.c the bulk of the code. sys/net/if.h new flag sys/net/if_var.h declaration for functions used in device drivers. sys/net/netisr.h NETISR_POLL sys/dev/fxp/if_fxp.c sys/dev/fxp/if_fxpvar.h sys/pci/if_dc.c sys/pci/if_dcreg.h sys/pci/if_sis.c sys/pci/if_sisreg.h device driver modifications
* Let M_LEADINGSPACE write into non-shared mbufs.luigi2001-12-141-1/+1
| | | | | | | | | A similar thing has been in -stable for weeks and is completely safe. This has very good performance implications as it saves some data copying, and sometimes avoids triggering performance bugs in devices (such as the "dc" and other Tulip clones) which do not like scattered data.
* Enable UFS_DIRHASH in the GENERIC kernel.iedowse2001-12-146-0/+6
| | | | | | Suggested by: silby Reviewed by: dillon MFC after: 5 days
* Fixed to draw mouse cursor. The syscons driver for PC98 uses differentnyan2001-12-146-18/+20
| | | | | | | attributes from i386. Submitted by: chi@bd.mbn.or.jp (Chiharu Shibata) MFC after: 3 days
* Bump __FreeBSD_version for userland smbfs import.sheldonh2001-12-141-1/+1
|
* o Clarify the comments on AIO to note that yes, AIO really is unsuitablerwatson2001-12-142-4/+4
| | | | | | for use on machines with untrusted local users, for security as well as stability reasons. o Lack of clarity pointed out by: David Rufino <dr@soniq.net> via bugtraq.
* Add disk I/O scheduling for positively niced processes.mckusick2001-12-141-0/+2
| | | | | | | | | When a positively niced process requests a disk I/O, make it wait for its nice value of ticks before scheduling its I/O request if there are any other processes with I/O requests in the disk queue. For all the gory details, see the ``Running fsck in the Background'' paper in the Usenix BSDCon 2002 Conference Proceedings, pages 55-64.
* Proper fix for old config setting maxusers to 8.peter2001-12-147-7/+7
|
* mdoc(7) police: remove hard sentence break which I didn'tru2001-12-141-1/+2
| | | | submit to Jonathan Mini.
* A slightly different version of the vlrureclaim fix.dillon2001-12-141-3/+1
| | | | Reported by: peter, ps
* Remove printf's on mbuf/cluster allocation failures. There are nowluigi2001-12-1414-82/+15
| | | | | | | equivalent and less dangerous (rate limited) messages in the mbuf allocation code. MFC after: 3 days
* Add disk I/O scheduling for positively niced processes.mckusick2001-12-141-0/+25
| | | | | | | | | When a positively niced process requests a disk I/O, make it wait for its nice value of ticks before scheduling its I/O request if there are any other processes with I/O requests in the disk queue. For all the gory details, see the ``Running fsck in the Background'' paper in the Usenix BSDCon 2002 Conference Proceedings, pages 55-64.
* Moved the updating of if_ibytes from ether_demux() to ether_input() to fixdg2001-12-141-1/+2
| | | | | | | a bug where the interface input bytes count wasn't updated when bridging is enabled. MFC after: 3 days
* Too many people are compiling kernels with maxusers set to 0 without the newdillon2001-12-141-1/+1
| | | | config. Hack the kernel to force auto-sizing if the old config is used.
* This fixes a large number of bugs in our NFS client side code. A recentdillon2001-12-146-11/+128
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | commit by Kirk also fixed a softupdates bug that could easily be triggered by server side NFS. * An edge case with shared R+W mmap()'s and truncate whereby the system would inappropriately clear the dirty bits on still-dirty data. (applicable to all filesystems) THIS FIX TEMPORARILY DISABLED PENDING FURTHER TESTING. see vm/vm_page.c line 1641 * The straddle case for VM pages and buffer cache buffers when truncating. (applicable to NFS client side) * Possible SMP database corruption due to vm_pager_unmap_page() not clearing the TLB for the other cpu's. (applicable to NFS client side but could effect all filesystems). Note: not considered serious since the corruption occurs beyond the file EOF. * When flusing a dirty buffer due to B_CACHE getting cleared, we were accidently setting B_CACHE again (that is, bwrite() sets B_CACHE), when we really want it to stay clear after the write is complete. This resulted in a corrupt buffer. (applicable to all filesystems but probably only triggered by NFS) * We have to call vtruncbuf() when ftruncate()ing to remove any buffer cache buffers. This is still tentitive, I may be able to remove it due to the second bug fix. (applicable to NFS client side) * vnode_pager_setsize() race against nfs_vinvalbuf()... we have to set n_size before calling nfs_vinvalbuf or the NFS code may recursively vnode_pager_setsize() to the original value before the truncate. This is what was causing the user mmap bus faults in the nfs tester program. (applicable to NFS client side) * Fix to softupdates (see ufs/ffs/ffs_inode.c 1.73, commit made by Kirk). Testing program written by: Avadis Tevanian, Jr. Testing program supplied by: jkh / Apple (see Dec2001 posting to freebsd-hackers with Subject 'NFS: How to make FreeBS fall on its face in one easy step') MFC after: 1 week
* Add maxusers auto-sizing description to NOTES file for -currentdillon2001-12-142-2/+6
|
* o Wording fix in comment.rwatson2001-12-141-1/+1
| | | | Submitted by: tanimura via p4
* Minimize the time necessary to suspend operations on a filesystemmckusick2001-12-144-96/+209
| | | | | | | | | | | | | | | | | | when taking a snapshot. The two time consuming operations are scanning all the filesystem bitmaps to determine which blocks are in use and scanning all the other snapshots so as to be able to expunge their blocks from the view of the current snapshot. The bitmap scanning is broken into two passes. Before suspending the filesystem all bitmaps are scanned. After the suspension, those bitmaps that changed after being scanned the first time are rescanned. Typically there are few bitmaps that need to be rescanned. The expunging of other snapshots is now done after the suspension is released by observing that we can easily identify any blocks that were allocated to them after the suspension (they will be maked as `not needing to be copied' in the just created snapshot). For all the gory details, see the ``Running fsck in the Background'' paper in the Usenix BSDCon 2002 Conference Proceedings, pages 55-64.
* Convert C++ style comments to proper C ones.obrien2001-12-1316-72/+87
| | | | | Clean up C comments just a tad. Fix ID's.
OpenPOWER on IntegriCloud