summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Assorted markup, grammar, and spelling fixes.ru2004-06-1315-359/+490
|
* Cast printf'ed values to intmax_t.obrien2004-06-131-3/+3
|
* Bump __FreeBSD_version for ALTQ. Also put some notes in UPDATING regardingmlaier2004-06-132-1/+7
| | | | the ABI break.
* Associate a device_t with an ACPI_HANDLE. This make AcpiWalkNamespace morenjl2004-06-132-0/+21
| | | | | useful. If ACPI-CA allowed null object handlers, we wouldn't need the placeholder function.
* Link ALTQ to the build and break with ABI for struct ifnet. Please recompilemlaier2004-06-1320-18/+302
| | | | | | | | | | | | your (network) modules as well as any userland that might make sense of sizeof(struct ifnet). This does not change the queueing yet. These changes will follow in a seperate commit. Same with the driver changes, which need case by case evaluation. __FreeBSD_version bump will follow. Tested-by: (i386)LINT
* Use NG_FREE_MSG() instead of FREE().phk2004-06-131-1/+1
|
* Remove a stale reference to %Ef and %EF from a comment.stefanf2004-06-131-2/+2
|
* Add the capacity for the rfc1490 node to handle cisco style encasulationjulian2004-06-133-25/+177
| | | | | | which is often used alongside rfc1490 in frame relay links. Submitted by: Gleb Smirnoff <glebius@cell.sick.ru>
* Add configuration rom entries for IP over firewire.dfr2004-06-132-0/+28
|
* To support the promiscuous mode udav(4) driversanpei2004-06-131-0/+24
| | | | | PR: kern/67862 Submitted by: WATANABE Shingo <nabe@nabechan.org>
* Paranoia, WARNS fixes and lint.markm2004-06-131-19/+19
|
* Be smarter about printing non-ethernet link-level addresses.dfr2004-06-131-3/+13
|
* Add a new driver to support IP over firewire. This driver is intended todfr2004-06-138-1/+1921
| | | | | | | | conform to the rfc2734 and rfc3146 standard for IP over firewire and should eventually supercede the fwe driver. Right now the broadcast channel number is hardwired and we don't support MCAP for multicast channel allocation - more infrastructure is required in the firewire code itself to fix these problems.
* Get rid of UMA zones and instead allocate all ecb's up front and track themscottl2004-06-132-25/+48
| | | | | | | | | | | | | | | | | | in a TAILQ. Re-arrange some of the ecb elements so that they can stay stable through alloc/free cycles while the rest get bzero'd. - Use the tag_id from the ecb rather than fro the ccb. The latter is only for target mode. - Honor the ccb flags for tag_action when deciding whether to do a tagged or untagged transaction. - Re-arrange autosense completion so that it works correctly in failure cases. - Turn on the PI_TAG_ABLE flag so that CAM will send us tagged transactions. This enables tagged queueing in the driver.
* make code less broken, only try to create unit 0 since there can onlyjmg2004-06-131-2/+4
| | | | | | | be one, this will help prevent multipling devices if this driver is ever loaded/unloaded multiple times... Prodded by: julian
* - Remove an unused declaration.alc2004-06-132-5/+4
| | | | - Move a definition inside the scope of a #ifdef _KERNEL.
* Socket MAC labels so_label and so_peerlabel are now protected byrwatson2004-06-1316-11/+104
| | | | | | | | | | | | | SOCK_LOCK(so): - Hold socket lock over calls to MAC entry points reading or manipulating socket labels. - Assert socket lock in MAC entry point implementations. - When externalizing the socket label, first make a thread-local copy while holding the socket lock, then release the socket lock to externalize to userspace.
* Prepare pf for building with ALTQ:mlaier2004-06-133-56/+4
| | | | | - remove old pfaltq module linkage - move pfaltq_running to pf_ioctl.c It is protected by PF_LOCK()
* Introduce socket and UNIX domain socket locks into hard-coded lockrwatson2004-06-131-1/+8
| | | | | | | | | | | | | | | | | order definition for witness. Send lock before receive lock, and socket locks after accept but before select: filedesc -> accept -> so_snd -> so_rcv -> sellck All routing locks after send lock: so_rcv -> radix node head All protocol locks before socket locks: unp -> so_snd udp -> udpinp -> so_snd tcp -> tcpinp -> so_snd
* Correct whitespace errors in merge from rwatson_netperf: tabs instead ofrwatson2004-06-121-5/+5
| | | | | | spaces, no trailing tab at the end of line. Pointed out by: csjp
* A first stab at truss support for amd64, basically cogged from i386.dwmalone2004-06-124-1/+353
| | | | It seems to work in my limited tests.
* Move #ifdef _KERNEL higher in socketvar.h to cover various socketrwatson2004-06-121-2/+2
| | | | buffer related macros.
* s/mbps/Mbps/cperciva2004-06-127-9/+9
| | | | | | | | We don't support any 10 millibit-per-second network cards. PR: docs/67719 Submitted by: Linh Pham MFC after: 1 week
* Add gvinum, the geom_vinum userland tool.le2004-06-123-0/+811
|
* Add a module directory for geom_vinum.le2004-06-121-0/+11
|
* Add a first version of a GEOMified vinum.le2004-06-1215-0/+5851
|
* Missed directory in previous commit; need to hold SOCK_LOCK(so)rwatson2004-06-121-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | before calling sotryfree(). -- Body of earlier bulk commit this belonged with -- Log: Extend coverage of SOCK_LOCK(so) to include so_count, the socket reference count: - Assert SOCK_LOCK(so) macros that directly manipulate so_count: soref(), sorele(). - Assert SOCK_LOCK(so) in macros/functions that rely on the state of so_count: sofree(), sotryfree(). - Acquire SOCK_LOCK(so) before calling these functions or macros in various contexts in the stack, both at the socket and protocol layers. - In some cases, perform soisdisconnected() before sotryfree(), as this could result in frobbing of a non-present socket if sotryfree() actually frees the socket. - Note that sofree()/sotryfree() will release the socket lock even if they don't free the socket. Submitted by: sam Sponsored by: FreeBSD Foundation Obtained from: BSD/OS
* Extend coverage of SOCK_LOCK(so) to include so_count, the socketrwatson2004-06-1220-8/+58
| | | | | | | | | | | | | | | | | | | | | | | | | reference count: - Assert SOCK_LOCK(so) macros that directly manipulate so_count: soref(), sorele(). - Assert SOCK_LOCK(so) in macros/functions that rely on the state of so_count: sofree(), sotryfree(). - Acquire SOCK_LOCK(so) before calling these functions or macros in various contexts in the stack, both at the socket and protocol layers. - In some cases, perform soisdisconnected() before sotryfree(), as this could result in frobbing of a non-present socket if sotryfree() actually frees the socket. - Note that sofree()/sotryfree() will release the socket lock even if they don't free the socket. Submitted by: sam Sponsored by: FreeBSD Foundation Obtained from: BSD/OS
* In a multiprocessor, the PG_W bit in the pte must be changed atomically.alc2004-06-122-3/+4
| | | | | | | Otherwise, the setting of the PG_M bit by one processor could be lost if another processor is simultaneously changing the PG_W bit. Reviewed by: tegge@
* Switch to using the "neworder" for rotating log files, by default. Thegad2004-06-121-1/+9
| | | | | | | main advantage of this is that daemon's are only signalled once per run, instead of once for each file that is rotated. MFC after: 2 weeks
* Add an additional queue which will be "owned by the driver". This allows tomlaier2004-06-121-0/+7
| | | | | | | | | | | | | | | | | | | | rig a PREPEND macro for ALTQ as the POLL/DEQUEUE semantic is very bad in terms of locking. We make this a full functional queue to allow "bulk dequeue" which will further reduce the locking overhead (for non-altq enabled devices). Drivers will access this via the following macros, which will show up in <net/if_var.h> once we expose ALTQ to the build: IFQ_DRV_DEQUEUE(ifq, m) - takes a mbuf off the queue (driver queue first) IFQ_DRV_PREPEND(ifq, m) - pushes a mbuf back to the driver queue IFQ_DRV_PURGE(ifq) - drops all packets in both queues IFQ_DRV_IS_EMPTY(ifq) - checks for pending mbufs in either queue One has to make sure that the first three are protected by a driver mutex. At the moment most network drivers still require Giant, so this is not an issue. Even those that have thier own mutex usually hold it in if_start and the like, so this requirement is almost always satisfied. This evolved from a discussion with Andrew Gallatin.
* Whitespace-only restyling of socket reference count macros.rwatson2004-06-121-25/+25
|
* Introduce a mutex into struct sockbuf, sb_mtx, which will be used torwatson2004-06-122-0/+31
| | | | | | | | | | | | | protect fields in the socket buffer. Add accessor macros to use the mutex (SOCKBUF_*()). Initialize the mutex in soalloc(), and destroy it in sodealloc(). Add addition, add SOCK_*() access macros which will protect most remaining fields in the socket; for the time being, use the receive socket buffer mutex to implement socket level locking to reduce memory overhead. Submitted by: sam Sponosored by: FreeBSD Foundation Obtained from: BSD/OS
* Fix registration of loadable line disciplines.phk2004-06-121-1/+2
| | | | This should make watch(8)/snp(4) work again.
* Group tinderbox results by config name. Skip configs whose names startdes2004-06-121-42/+54
| | | | with "update_".
* Include the config name in the log file name.des2004-06-121-1/+8
|
* Check pending signals, if there is signal will be unblocked bydavidxu2004-06-128-44/+50
| | | | | | | | | | | | | | | | | | sigsuspend, thread shouldn't wait, in old code, it may be ignored. When a signal handler is invoked in sigsuspend, thread gets two different signal masks, one is in thread structure, sigprocmask() can retrieve it, another is in ucontext which is a third parameter of signal handler, the former is the result of sigsuspend mask ORed with sigaction's sa_mask and current signal, the later is the mask in thread structure before sigsuspend is called. After signal handler is called, the mask in ucontext should be copied into thread structure, and becomes CURRENT signal mask, then sigsuspend returns to user code. Reviewed by: deischen Tested by: Sean McNeil <sean@mcneil.com>
* Remove an unused #include.alc2004-06-121-1/+0
|
* When autosense is retrieved, tell CAM about it instead of juust pretendingscottl2004-06-121-1/+2
| | | | | | | that the command succeeded. Sheesh! This makes CDROMs no longer cause an instant panic at boot. Thanks to Jake Burkholder for providing a remote test setup. Also make device resets work, thanks to another typo.
* The references to scalbn and scalbnf should be scalb and scalbf.das2004-06-121-2/+5
| | | | | | (The former are actually useful, and ieee_test(3) only documents functions that aren't.) Add a sentence describing the domain of scalb() and scalbf().
* Correct typo from previous commit.scottl2004-06-121-1/+1
|
* Back out 1.23 until I figure out why it causes Netra t1 100 to no longermarius2004-06-121-1/+1
| | | | | | pass any traffic. Unfortunately this means no full-duplex link with auto- negotiation on hme(4) using DP83840A PHYs again. I really thought I had tested this also on a Netra t1 100...
* FreeBSD-ify ALTQ:mlaier2004-06-129-21/+164
| | | | | | | | | | | | | | | | | | - add locking - disable ALTQ3_COMPAT by default (do not remove the code to keep the diff towards KAME small) - put some more code under ALTQ3 conditional compilation as it should be - account for if_xname - some more minor compile fixes As people started wondering: The strange path layout "altq/altq" is there to avoid "-Isys/contrib" and make it "-Isys/contrib/altq" instead, as we will need at least <altq/altq.h> and <altq/if_altq.h> for kernel compilation. The "freebsd4_..." in the privious commit is just the best tag name in the KAME tree I could find to classify this in order to track its history. It does *not* mean that this will go to 4-STABLE or anything of that kind.
* This commit was generated by cvs2svn to compensate for changes in r130365,mlaier2004-06-1221-0/+14567
|\ | | | | | | which included commits to RCS files with non-trunk default branches.
| * Import parts of the ALTQ framework from latest KAME snapshot (which is up tomlaier2004-06-1221-0/+14567
| | | | | | | | | | | | | | | | | | | HEAD at this point). This will not exactly live in a vendor branch, but have the vendor backing to make it easier to exchange diffs. This will be followed by a diff which takes most of the .c files off the vendor branch in order to: - add locking - disable ALTQ3_COMPAT code (which is outdated and "un-lockable") There is work in progress to refine the configuration API. Import this "as is" now to have more exposure time before 5-STABLE. This is only the import, it will be some more days until you will actually be able to compile ALTQ support into your kernel so don't hold your breath. HEADUPs will be posted on current@ and net@ before this is actually enabled. No-objection: re(scottl), core(rwatson)
* Use tabs instead of spaces between #define and macro name; a mergerwatson2004-06-111-2/+2
| | | | mistake as they are in rwatson_netperf.
* Modify ip fw so that whenever UID or GID constraints exist in acsjp2004-06-111-30/+77
| | | | | | | | | | | | | | | | | | | ruleset, the pcb is looked up once per ipfw_chk() activation. This is done by extracting the required information out of the PCB and caching it to the ipfw_chk() stack. This should greatly reduce PCB looking contention and speed up the processing of UID/GID based firewall rules (especially with large UID/GID rulesets). Some very basic benchmarks were taken which compares the number of in_pcblookup_hash(9) activations to the number of firewall rules containing UID/GID based contraints before and after this patch. The results can be viewed here: o http://people.freebsd.org/~csjp/ip_fw_pcb.png Reviewed by: andre, luigi, rwatson Approved by: bmilekic (mentor)
* Neither pmap_enter() nor pmap_enter_quick() should create pv entries foralc2004-06-111-4/+10
| | | | | | unmanaged pages. Tested by: marcel@
* Move uma_small_alloc() and uma_small_free() out of the pmap and into theiralc2004-06-113-46/+83
| | | | | own machine-dependent file. This makes alpha consistent with amd64, ia64, and powerpc.
* Style cleanup.schweikh2004-06-111-64/+81
|
OpenPOWER on IntegriCloud