summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Tidy up pmap_ts_referenced(): Eliminate excessive white space. Eliminatealc2006-07-011-11/+1
| | | | | | | an initialized but otherwise unused variable. Explicitly check a pointer against NULL. There are no functional changes. Checked by: md5
* Eliminate the acquisition and release of Giant from moea_extract_and_hold()alc2006-07-012-12/+0
| | | | | | and moea_protect(). Tested by: grehan@ and rink@
* Grammar nit.ru2006-07-011-1/+1
|
* Use some math tricks in arena_run_reg_dalloc() to avoid actual division, asjasone2006-07-011-83/+90
| | | | | | | | | | | | | | | | | well as avoiding a switch statement. This change has no significant impact to performance when branch prediction is successful at predicting the sizes of objects passed to free(), but in the case that the object sizes are semi-random, this change has the potential to prevent many branch prediction misses, thus improving performance substantially. Take advantage of alignment guarantees in ipalloc(), and pad object sizes to something less than a power of two when possible. This has the potential to substantially reduce internal fragmentation for objects allocated via posix_memalign(). Avoid an unnecessary pow2_ceil() call in arena_ralloc(). Submitted by: djam8193ah@hotmail.com
* More grammar / wording nit fixes, starting in the boot loader sectionbmah2006-07-012-30/+34
| | | | and continuing through the multimedia support section.
* o Remove rev. 1.30 leftover. From Damien: However, this code pathmaxim2006-07-011-1/+1
| | | | | | | | | | is never taken since there aren't any 802.11a ural(4) sticks available on the market. PR: kern/99676 Submitted by: KIYOHARA Takashi Reviewed by: damien MFC after: 1 week
* Housekeeping. Update for maintainers who have handed in their commit bitsmarkm2006-07-016-23/+0
| | | | or (in my case) no longer feel that oversight is necessary.
* Eliminate the remaining uses of "register".alc2006-07-011-27/+13
| | | | Convert the remaining K&R-style function declarations to ANSI-style.
* Add __{BEGIN,END}_DECLS macros, so that function prototypes remainjasone2006-06-301-0/+4
| | | | | | unmangled for C++ programs. Submitted by: Niklas Sorensson <nik@cs.chalmers.se>
* Make the behavior of malloc(0) standards-compliant by getting rid of nil,jasone2006-06-301-48/+46
| | | | | | | | | and instead creating a small allocation for each malloc(0) call. The optional SysV compatibility behavior remains unchanged. Add a couple of assertions. Fix a couple of typos in error message strings.
* Fix kernel module build breakage.jkim2006-06-301-0/+2
|
* o fix join/rejoin formatsam2006-06-301-2/+22
| | | | | | o add netbsd portability glue MFC after: 2 weeks
* Change mfi_add_ld to "immediate command" mode since we need to enumerateambrisko2006-06-301-4/+7
| | | | | | potential boot disks during the probe so they are read for mount root. Reviewed by: ps, scottl
* We needn't check "m" for NULL here because "off" should be withinyar2006-06-301-1/+1
| | | | | | | | | | the mbuf chain. If we ever get a buggy caller, a bogus "off" should be caught by the sanity check at the function entry. Null "m" here means a very unusual condition of a totally broken mbuf chain (wrong m_pkthdr.len or whatever), so we can just page fault later. Found by: Coverity Prevent(tm) CID: 825
* Gleb committed an intermediary version, commit the right one now.ru2006-06-301-10/+11
| | | | Submitted by: Vadim Goncharov
* - Simplify the formatting in the SYNOPSIS.ru2006-06-302-4/+3
| | | | - Add the forgotten new option in usage().
* o Fix typo in the comment.maxim2006-06-301-1/+1
| | | | | PR: kern/99632 Submitted by: clsung
* - Reflect recent sched_core(4) changes.delphij2006-06-301-10/+22
| | | | - Some typo fixes.
* Have sio return BIS_PROBE_DEFAULT like all the other drivers in theimp2006-06-301-2/+2
| | | | | | | | | | | | tree... John Baldwin noted that sio might pass values between probe and attach via softc. It appears that sio does leave the hardware in a known state after probing, so other drivers that try to probe might leave it in a worse state. It doesn't seem to pass any data in softc, however, that I could find... I think we should not be probing for anything but nonPnP isa, but that's a change for another day. Submitted by: Frank Behrens PR: 87845
* Add a -q option to suppress header lines when multiple files are specified.flz2006-06-294-8/+19
| | | | | Approved by: cperciva (mentor) MFC after: 1 week
* Create new dialect knob, as setting the language dialect isn't a warning flag.obrien2006-06-292-2/+3
|
* Partial support for branch long emulation. This only emulates themarcel2006-06-294-1/+112
| | | | | branch long jump and not the branch long call. Support for that is forthcoming.
* Fix building with GCC 4.2: define data types before referring to them.obrien2006-06-291-0/+1
|
* There is a consensus that ifaddr.ifa_addr should never be NULL,yar2006-06-2911-50/+28
| | | | | | | | | | except in places dealing with ifaddr creation or destruction; and in such special places incomplete ifaddrs should never be linked to system-wide data structures. Therefore we can eliminate all the superfluous checks for "ifa->ifa_addr != NULL" and get ready to the system crashing honestly instead of masking possible bugs. Suggested by: glebius, jhb, ru
* Use TAILQ_FOREACH in the __FreeBSD__ case, too.yar2006-06-291-2/+1
| | | | Funnily enough, rev. 1.15 changed the __Net and __Open cases only.
* Use TAILQ_FOREACH.yar2006-06-291-4/+1
|
* Use the nifty TAILQ_FOREACH.yar2006-06-291-2/+1
|
* Use TAILQ_FOREACH consistently.yar2006-06-291-2/+1
|
* Use queue(3) macros instead of accessing list/queue internals directly.yar2006-06-291-3/+3
|
* Fix building with GCC 4.2: ensure types are defined before refering to them.obrien2006-06-295-5/+5
|
* Use the elegant TAILQ_FOREACH() in place of a hand-rolled for() loop.yar2006-06-291-3/+1
|
* Fix semctl(2) breakage from the previous commit. Previously __semctl() hadjhb2006-06-291-7/+12
| | | | | | | | | | | | | a local 'semid' variable which was the array index and used uap->semid as the original IPC id. During the kern_semctl() conversion those two variables were collapsed into a single 'semid' variable breaking the places that needed the original IPC ID. To fix, add a new 'semidx' variable to hold the array index and leave 'semid' unmolested as the IPC id. While I'm here, explicitly document that the (undocumented, at least in semctl(2)) SEM_STAT command curiously expects an array index in the 'semid' parameter rather than an IPC id. Submitted by: maxim
* Fix URL to Bellovin's paper.glebius2006-06-291-1/+1
| | | | Submitted by: Anton Yuzhaninov <citrin rambler-co.ru>
* Fix a bug when accumulating run time, if a thread calls yield() syscall,davidxu2006-06-291-5/+5
| | | | its run time may be lost.
* Eliminate the offset argument from send_reject. It's not beenbz2006-06-291-9/+7
| | | | | | | | used since FreeBSD-SA-06:04.ipfw. Adopt send_reject6 to what had been done for legacy IP: no longer send or permit sending rejects for any but the first fragment. Discussed with: oleg, csjp (some weeks ago)
* Use INPLOOKUP_WILDCARD instead of just 1 more consistently.bz2006-06-295-9/+15
| | | | OKed by: rwatson (some weeks ago)
* Fix system load count (noticed by dephij). Remove incorrectdavidxu2006-06-291-6/+1
| | | | comment.
* Correct a typodelphij2006-06-291-1/+1
|
* Update man page.takawata2006-06-291-0/+2
| | | | | Pointed out by: netchild MFC after: 3 days
* Detach the interface first, do vlan_unconfig() then.yar2006-06-291-9/+3
| | | | | | | | | | | | | | | Previously, another thread could get a pointer to the interface by scanning the system-wide list and sleep on the global vlan mutex held by vlan_unconfig(). The interface was gone by the time the other thread woke up. In order to be able to call vlan_unconfig() on a detached interface, remove the purely cosmetic bzero'ing of IF_LLADDR from the function because a detached interface has no addresses. Noticed by: a stress-testing script by maxim Reviewed by: glebius
* Remove a few unused things.yar2006-06-291-12/+8
| | | | Fix some style and consistency points.
* Reduce unneeded code duplication.yar2006-06-291-12/+1
|
* Since 5714 family doesn't have Jumbo ring, we do not supportglebius2006-06-291-3/+0
| | | | | | Jumbos on them, yet. The 5780 is equivalent to the 5714. Submitted by: brad@OpenBSD, davidch
* Comment fix.takawata2006-06-291-2/+2
| | | | Pointed out by: ume via IRC
* Willcom WSIM DD support.takawata2006-06-292-1/+4
|
* Remove unused function declaration.davidxu2006-06-291-4/+2
| | | | | Add else statement in sched_calc_pri. Fix a bug when checking interrupt thread in sched_add.
* Remove load balancer code, since it has serious priority inversion problemdavidxu2006-06-291-1011/+413
| | | | which really hurts performance on FreeBSD.
* A small race existed where the lock was dropped between when encif wasthompsa2006-06-281-24/+20
| | | | | | | | | | | | tested and then set. [1] Reorganise things to eliminate this, we now ensure that enc0 can not be destroyed which as the benefit of no longer needing to lock in ipsec_filter and ipsec_bpf. The cloner will create one interface during the init so we can guarantee that encif will be valid before any SPD entries are added to ipsec. Spotted by: glebius [1]
* Properly detect the RTL8168(B?) again. RealTek sent me a bunch of samplewpaul2006-06-282-2/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | cards: the chips are all marked "RTL8111B", but they put stickers on the back that say "RTL8168B/8111B". The manual says there's only one HWREV code for both the 8111B and 8168B devices, which is 0x30000000, but the cards they sent me actually report HWREV of 0x38000000. Deciding to trust the hardware in front of me rather than a possibly incorrect manual (it wouldn't be the first time the HWREVs were incorrectly documented), I changed the 8168 revision code. It turns out this was a mistake though: 0x30000000 really is a valid for the 8168. There are two possible reasons for there to be two different HWREVs: 1) 0x30000000 is used only for the 8168B and 0x38000000 is only for the 8111B. 2) There were 8111/8168 rev A devices which both used code 0x30000000, and the 8111B/8168B both use 0x38000000. The product list on the RealTek website doesn't mention the existence of any 8168/8111 rev A chips being in production though, and I've never seen one, so until I get clarification from RealTek, I'm going to assume that 0x30000000 is just for the 8168B and 0x38000000 is for the 8111B only. So, the HWREV code for the 8168 has been put back to 0x30000000, a new 8111 HWREV code has been added, and there are now separate entries for recognizing both devices in the device list. This will allow all devices to work, though if it turns out I'm wrong I may need to change the ID strings
* Dont call free on non-alloc'd items.sos2006-06-281-2/+4
|
OpenPOWER on IntegriCloud