summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* destroy child devices on detach to prevent ever-increasing numbers ofcg2001-03-171-7/+10
| | | | | pcm/midi devices trying to attach if the module is repeatedly loaded and unloaded.
* Merged from sys/i386/conf/GENERIC revision 1.305 (moved the fxp driverkato2001-03-171-1/+1
| | | | into the miibus section.)
* Add a new entrypoint to the hashes in libmd:phk2001-03-171-0/+1
| | | | | | | | | char * FooFileChunk(const char *filename, char *buf, off_t offset, off_t length) Which only hashes part of a file. Implement FooFile() in terms of this function. Submitted by: roam
* Use a generic implementation of the Fowler/Noll/Vo hash (FNV hash).peter2001-03-1714-78/+86
| | | | | | | | | | | | | | | | | Make the name cache hash as well as the nfsnode hash use it. As a special tweak, create an unsigned version of register_t. This allows us to use a special tweak for the 64 bit versions that significantly speeds up the i386 version (ie: int64 XOR int64 is slower than int64 XOR int32). The code layout is a little strange for the string function, but I was able to get between 5 to 10% improvement over the original version I started with. The layout affects gcc code generation choices and this way was fastest on x86 and alpha. Note that 'CPUTYPE=p3' etc makes a fair difference to this. It is around 45% faster with -march=pentiumpro on a p6 cpu.
* Dramatically improve the **lame** nfs_hash(). This is based on thepeter2001-03-172-16/+32
| | | | | | | | | | | | | Fowler / Noll / Vo Hash (http://www.isthe.com/chongo/tech/comp/fnv/). This improves hash coverage a *massive* amount. We were seeing one set of machines that were using 0.84% of their 131072 entry nfsnode hash buckets with maximum chain lengths of up to ~500 entries. The machine was spending nearly 100% of its time in 'system'. A test with this has pushed the coverage from a few perCent up to 91% utilization with a max chain length of 11. Submitted by: David Filo
* Fix the building of the aac driver as a module. Add a comment about enablingscottl2001-03-171-1/+2
| | | | debug information for the driver.
* Always call resource_int_value function for getting portsize and msize.nyan2001-03-171-4/+6
| | | | | | It was not set resource size (portsize/msize) if resource address was set. This is MFC candidate.
* Really fix NWAY negotiation for the 82553 PHY. Locking down thejlemon2001-03-171-2/+12
| | | | | | | media interface selection should not imply disabling NWAY negotiaton as well. Problem pointed out by: peter
* This is an MFC candidate.gibbs2001-03-173-2/+6
| | | | | | | | | | | | Add the AAC_DEBUG option to enable debugging in the aac driver. Correct a race condition in the interrupt handler where the controller may queue a fib to a response queue after the driver has serviced the queue but before the interrupt is cleared. This could leave a completed fib stranded in the response queue unless another I/O completed and generated another interrupt. Reviewed by: msmith
* Add the AAC_DEBUG option to enable debugging in the aac driver.gibbs2001-03-172-1/+9
| | | | Reviewed by: msmith
* When doing a recv(.. MSG_WAITALL) for a message which is larger thanjlemon2001-03-161-0/+6
| | | | | | | | | | | the socket buffer size, the receive is done in sections. After completing a read, call pru_rcvd on the underlying protocol before blocking again. This allows the the protocol to take appropriate action, such as sending a TCP window update to the peer, if the window happened to close because the socket buffer was filled. If the protocol is not notified, a TCP transfer may stall until the remote end sends a window probe.
* Fix a few things in the aic(4) driver:ken2001-03-164-7/+47
| | | | | | | | | | - enable 10MHz (fast SCSI) operation on boards that support it. (only aic6360 boards with fast SCSI enabled can do it) - bounds check sync periods and offsets passed in from the transport layer - tell the user which resource allocation failed (for the ISA probe) if we weren't able to allocate an IRQ, DRQ or I/O port.
* Fix inquiry length detection for the ses(4) driver. It was using theken2001-03-161-4/+4
| | | | | | | | | | | inq_len member of the ccb_getdev structure, but we've never filled that value in.. So we now get the length from the inquiry data returned by the drive. (Since we will fetch as much inquiry data as the drive claims to support.) Reviewed by: mjacob Reported by: Andrzej Tobola <san@iem.pw.edu.pl>
* prevent gdb from panic'ing an alpha with "mutex Giant not owned"gallatin2001-03-161-0/+2
| | | | reviewed by: jhb
* Fix a typo which would cause containers between 1GB and 2GB to have the wrongmsmith2001-03-161-1/+1
| | | | | | geometry reported. Submitted by: mark tinguely <tinguely@web.cs.ndsu.NoDak.edu>
* fix a typo preventing the second dma channel being releasedcg2001-03-161-1/+3
| | | | use isa_dma_release when releasing dma channels
* don't leak memory allocated for feeders at module unloadcg2001-03-163-1/+22
| | | | kill the fake channel when unregistering
* <sys/queue.h> makeover.phk2001-03-166-56/+48
|
* Fix a style(9) nit.phk2001-03-161-1/+1
|
* nuke IPSEC_SRCSEL which does not do the right thing.ume2001-03-161-33/+3
| | | | | | | adjust state->ro if the tunnel endpoint is offlink. KAME PR 233. PR: kern/21079
* Enable some undocumented bits in the DP83840 PHY, which is neededjlemon2001-03-161-5/+8
| | | | | | | when using it with the Intel fxp driver. Tested by: peter, Ollivier Robert <roberto@eurocontrol.fr>, Peter Schultz <pete@jocose.org>
* Sigh, try to get this in sync with an offical src tree...sos2001-03-161-2/+0
| | | | I hate it when this happens...
* Remove the now defunct ATA_ENABLE* optionssos2001-03-165-23/+0
| | | | Spotted by: phk
* Merge from kame (1.175 -> 1.176):kuriyama2001-03-161-1/+27
| | | | cope with freebsd4 bridge code.
* add cnw driver to notes/lintimp2001-03-162-0/+4
|
* Add cwn driverimp2001-03-161-0/+2
|
* Commit port of cnw driver from Hiroyuki Aizu-san. This driverimp2001-03-163-0/+2006
| | | | | | | | | | | | supports Xircom netwave series of cards. I have one of these cards (but am trying to find one or two to test with), but it compiles and aizu-san says it works. I don't know if this supports 802.11 or not. I've seen conflicting information on this. Submitted by: Hiroyuki Aizu <aizu@jaist.ac.jp> Obtained from: NetBSD
* Remove the SMART ioctls, they are not in the official sources yet..sos2001-03-161-2/+0
| | | | This should restore world...
* Resync to GENERIC. This backs out the spammage that I committed wrtimp2001-03-161-23/+15
| | | | | | | | killing ipv6 and some other things. This makes GENERIC and NEWCARD the same, with OLDCARD stuff commented out and the NEWCARD stuff included. For the moment, pcic is commented out (which has a old). Plus invariants. Plus ddb.
* Hmm, the last commit apparently only made it halfwayssos2001-03-151-2/+0
|
* Remove the ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC and ATA_ENABLE_TAGSsos2001-03-151-1/+0
| | | | options, use the tuneables listed in ata.4 instead.
* Provide the interface to atacontrol and associated logic.sos2001-03-1510-455/+503
| | | | | | | | | see atacontrol(8) for more. Also the ATA_ENABLE_ATAPI_DMA, ATA_ENABLE_WC and ATA_ENABLE_TAGS options are gone, use the tuneables listed in ata.4 instead from the loader (this makes it possible to switch off DMA before the driver has to touch the devices on broken hardware).
* Add the ata control device.sos2001-03-151-1/+1
|
* net/route.c:ru2001-03-153-13/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A route generated from an RTF_CLONING route had the RTF_WASCLONED flag set but did not have a reference to the parent route, as documented in the rtentry(9) manpage. This prevented such routes from being deleted when their parent route is deleted. Now, for example, if you delete an IP address from a network interface, all ARP entries that were cloned from this interface route are flushed. This also has an impact on netstat(1) output. Previously, dynamically created ARP cache entries (RTF_STATIC flag is unset) were displayed as part of the routing table display (-r). Now, they are only printed if the -a option is given. netinet/in.c, netinet/in_rmx.c: When address is removed from an interface, also delete all routes that point to this interface and address. Previously, for example, if you changed the address on an interface, outgoing IP datagrams might still use the old address. The only solution was to delete and re-add some routes. (The problem is easily observed with the route(8) command.) Note, that if the socket was already bound to the local address before this address is removed, new datagrams generated from this socket will still be sent from the old address. PR: kern/20785, kern/21914 Reviewed by: wollman (the idea)
* Add new ATA specific file, to be used with the upcoming atacontrol.sos2001-03-151-0/+207
|
* Add a placeholder for the ServerWorks OSB4 device id. The SMBuspeter2001-03-151-0/+4
| | | | | | interface on this chip is compatable with the PIIX4. The catch is that this interferes with isab0 which wants to attach to the same PCI node. It seems to work, but we only tested it on systems with no ISA cards.
* The serverworks OSB4 pci->isa bridge has the same mapping register atpeter2001-03-151-3/+3
| | | | offset 0x90 for the SMBus device as the PIIX4.
* Kill the 4MB kernel limit dead. [I hope :-)].peter2001-03-1512-28/+72
| | | | | | | | | | | | | | | For UP, we were using $tmp_stk as a stack from the data section. If the kernel text section grew beyond ~3MB, the data section would be pushed beyond the temporary 4MB P==V mapping. This would cause the trampoline up to high memory to fault. The hack workaround I did was to use all of the page table pages that we already have while preparing the initial P==V mapping, instead of just the first one. For SMP, the AP bootstrap process suffered the same sort of problem and got the same treatment. MFC candidate - this breaks on 4.x just the same.. Thanks to: Richard Todd <rmtodd@ichotolot.servalan.com>
* Jake essentially rewrote this. It is not by any stretch of thepeter2001-03-151-2/+0
| | | | imagination a derivative of what I did before.
* Regenerate after rwatson's commit to syscalls.master (rev 1.85)peter2001-03-156-7/+11
|
* This include file has no business being here.mdodd2001-03-151-2/+0
|
* o Change the API and ABI of the Extended Attribute kernel interfaces torwatson2001-03-1517-172/+333
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | introduce a new argument, "namespace", rather than relying on a first- character namespace indicator. This is in line with more recent thinking on EA interfaces on various mailing lists, including the posix1e, Linux acl-devel, and trustedbsd-discuss forums. Two namespaces are defined by default, EXTATTR_NAMESPACE_SYSTEM and EXTATTR_NAMESPACE_USER, where the primary distinction lies in the access control model: user EAs are accessible based on the normal MAC and DAC file/directory protections, and system attributes are limited to kernel-originated or appropriately privileged userland requests. o These API changes occur at several levels: the namespace argument is introduced in the extattr_{get,set}_file() system call interfaces, at the vnode operation level in the vop_{get,set}extattr() interfaces, and in the UFS extended attribute implementation. Changes are also introduced in the VFS extattrctl() interface (system call, VFS, and UFS implementation), where the arguments are modified to include a namespace field, as well as modified to advoid direct access to userspace variables from below the VFS layer (in the style of recent changes to mount by adrian@FreeBSD.org). This required some cleanup and bug fixing regarding VFS locks and the VFS interface, as a vnode pointer may now be optionally submitted to the VFS_EXTATTRCTL() call. Updated documentation for the VFS interface will be committed shortly. o In the near future, the auto-starting feature will be updated to search two sub-directories to the ".attribute" directory in appropriate file systems: "user" and "system" to locate attributes intended for those namespaces, as the single filename is no longer sufficient to indicate what namespace the attribute is intended for. Until this is committed, all attributes auto-started by UFS will be placed in the EXTATTR_NAMESPACE_SYSTEM namespace. o The default POSIX.1e attribute names for ACLs and Capabilities have been updated to no longer include the '$' in their filename. As such, if you're using these features, you'll need to rename the attribute backing files to the same names without '$' symbols in front. o Note that these changes will require changes in userland, which will be committed shortly. These include modifications to the extended attribute utilities, as well as to libutil for new namespace string conversion routines. Once the matching userland changes are committed, a buildworld is recommended to update all the necessary include files and verify that the kernel and userland environments are in sync. Note: If you do not use extended attributes (most people won't), upgrading is not imperative although since the system call API has changed, the new userland extended attribute code will no longer compile with old include files. o Couple of minor cleanups while I'm there: make more code compilation conditional on FFS_EXTATTR, which should recover a bit of space on kernels running without EA's, as well as update copyright dates. Obtained from: TrustedBSD Project
* remove bogus check -- for kernel threads we fork off of proc0, not curprocgallatin2001-03-153-6/+0
| | | | | | | This was causing panics when modules which create kthreads were loaded after boot. pointed out by: jake, jhb
* Don't set the gateway address if the netmask is zero or we're onps2001-03-141-1/+5
| | | | | | | the same network. PXE does not do netmask calculations, so if the gateway is set it will use it. Submitted by: peter & FreeBSD cluster ACLs
* Use better descriptions (ones invovling words from the English languagejhb2001-03-141-2/+2
| | | | anyways) for the accept filter modules.
* Add some performance features to the fxp driver. If the chip is notjlemon2001-03-143-28/+74
| | | | | | | | | a 82557 (e.g.: a newer chip) then: + enable MWI, if the PCI configuration indicates the system supports it + enable usage of extended TxCB, for better performance + enable hardware flow control. FC frames will be passed up to the host only if promiscuous mode is enabled.
* o In my merge, missed the one-line patch to ufs_vnops.c that removedrwatson2001-03-141-1/+0
| | | | | | | the static prototype for ufs_readdir(). Note that ufs_readdir() was actually already non-static, the prototype was incorrect. Submitted by: jedgar
* Improve comments about the sound drivers.dcs2001-03-141-4/+4
| | | | Correct accf lines.
* Minor cleanup to the previous commit:sos2001-03-144-15/+20
| | | | | | Print what devices went away and which arrived. Avoid timeout loop on missing status.
* Add support for the IOMEGA Clik!sos2001-03-141-0/+16
| | | | | | IOMEGA deserves a medal for making the most nonstandard ATAPI devices, if they are ignorant or just not smart enough I don't know, but somebody should help them out of their misery...
OpenPOWER on IntegriCloud