summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* (Mostly) teach ath_rate_sample about MCS rates.adrian2011-01-282-94/+246
| | | | | | | | | | | | | | This is just the bare minimum needed to teach ath_rate_sample to try and handle MCS rates. It doesn't at all attempt to find the best rate by any means - it doesn't know anything about the MCS rate relations, TX aggregation or any of the much sexier 11n stuff that's out there. It's just enough to transmit 11n frames and handle TX completion. It shouldn't affect legacy (11abg) behaviour. Obtained from: rpaulo@
* Make space for the extended 802.11n MCS rate tables.adrian2011-01-281-1/+1
|
* Bring in some 802.11n packet duration calculation functions from a mix of ↵adrian2011-01-282-1/+86
| | | | | | | | | Sam/Rui and linux ath9k . This will eventually be used by rate control modules and by the TX code for calculating packet duration when handling rts/cts protection. Obtained from: sam@, rpaulo@, linux ath9k
* - Remove double semicolon.hselasky2011-01-281-6/+5
| | | | | | | | | - Remove reference to sprintf. Use printf directly. This part of the code should be optimised further to avoid many small printouts. Setting a sensible line buffer length could help aswell when printing out megabytes of data per second. Approved by: thompsa (mentor)
* CDDL fixes for MIPS n32.jchandra2011-01-282-3/+5
| | | | Provide 64 bit atomic ops, and use 32 bit pointer.
* Style(9) fix.dchagin2011-01-281-1/+1
| | | | MFC after: 1 month.
* sh: Add test for EXIT trap in command substitution.jilles2011-01-271-0/+3
| | | | This is not really realistic but is an opposition to $(trap).
* linux_sigreturn() loads the struct trapframe from l_sigcontextkib2011-01-271-22/+22
| | | | | | | | | | | | | | members, thus making a signed extension of 32 bit register context. If the register is not touched in usermode between return from signal and next syscall entry, the sign-extension part of 64bit register is not cleared, causing linux32_fetch_syscall_args() to read wrong values. Use unsigned type for the registers in the linux sigcontext. Reported by: Jacob Frelinger <jacob.frelinger duke edu>, arundel In collaboration with: dchagin MFC after: 1 week
* ixgb(4) does not support altq(4) yet.yongari2011-01-271-1/+0
|
* Backout r216577. ixgb(4) does not support altq(4) yet.yongari2011-01-271-2/+1
|
* Remember created control connection so on fork(2) we can close it in child.pjd2011-01-272-0/+4
| | | | | Found with: procstat(1) MFC after: 1 week
* Close the control socket before exiting, so it will be unlinked.pjd2011-01-271-0/+1
| | | | MFC after: 1 week
* Extend pjdlog_verify() to support the following additional macros:pjd2011-01-272-9/+44
| | | | | | | | | | PJDLOG_RVERIFY() - always check expression and on false log the given message and exit. PJDLOG_RASSERT() - check expression when NDEBUG is not defined and on false log given message and exit. PJDLOG_ABORT() - log the given message and exit. MFC after: 1 week
* Add functions to initialize/finalize pjdlog. This allows to open/close logpjd2011-01-274-1/+72
| | | | | | file at will. MFC after: 1 week
* Use my copyright for 2011 work.pjd2011-01-271-1/+2
| | | | MFC after: 1 week
* Add LOG_NDELAY flag to openlog(3) - we want descriptor to be immediately openpjd2011-01-271-1/+1
| | | | | | so there are no surprises once we start chrooting or using capsicum. MFC after: 1 week
* - Remove obvious NOTREACHED comment after abort() call.pjd2011-01-271-3/+1
| | | | | | - Remove redundant newline at the end of the file. MFC after: 1 week
* Remove __dead2 from pjdlog_verify() prototype, it does return sometimes.pjd2011-01-271-1/+1
| | | | MFC after: 1 week
* Add support for BIO_DELETE on swap-backed md(4). In the case of BIO_DELETEkib2011-01-271-6/+10
| | | | | | | | | | | covering the whole page, free the page. Otherwise, clear the region and mark it clean. Not marking the page dirty could reinstantiate cleared data, but it is allowed by BIO_DELETE specification and saves unneeded write to swap. Reviewed by: alc Tested by: pho MFC after: 2 weeks
* Implement sf_buf using direct map (XKPHYS) in MIPS n64.jchandra2011-01-273-3/+40
| | | | | | | | | | - Provide trivial implementation of sf_buf_alloc(), sf_buf_free(), sf_buf_kva() and sf_buf_page() using direct map for n64. - uio_machdep.c - use macros so that the direct map will be used in case of n64. Reviewed by: imp (earlier version) Obtained from: jmallett (user/jmallett/octeon)
* Fix n32 compile.jchandra2011-01-275-5/+7
| | | | | | | These changes are needed to fix n32 compile after the recent change of mips n32 MACHINE_ARCH to mipsn32eb/mipsn32el. Reviewed by: imp, bz (earlier version)
* Initialise the chainmask from the EEPROM rather than the hard-coded defaults.adrian2011-01-271-0/+30
| | | | | | | | | | | | | The defaults enabled three chains on the AR5416 even if the card has two chains. This restores that and ensures that only the correct TX/RX chainmasks are used. When HT modes are enabled, all TX chains will be correctly enabled. This should now enable analog chain swapping with 2-chain cards. I'm not sure if this is needed for just the AR5416 or whether it also applies to AR9160, AR9280 and AR9287 (later on); I'll have to get clarification.
* Add missing getCapability call for AR5416.adrian2011-01-271-4/+4
|
* While inspecting the disklabel check that start offset of partition isae2011-01-271-0/+3
| | | | | | | within provider's bounds. If not then reject this disklabel. Mark bbarea as NULL to do not free it again in destroy method. MFC after: 1 week
* Make a note to re-check whether that particular check is needed.adrian2011-01-271-0/+2
|
* Quick fix to a comment.gnn2011-01-271-2/+2
|
* Writing to the analog registers on the AR9220 (Merlin PCI) seems to require ↵adrian2011-01-271-0/+9
| | | | | | | | | | | a delay. This, along with an initval change which will appear in a subsequent commit, fixes bus panics that I have been seing with the AR9220 on a Routerstation Pro (AR7161 MIPS board.) Obtained from: Linux ath9k PR: kern/154220
* Explicitly wire the user buffer rather than doing it implicitly inmdf2011-01-2710-10/+46
| | | | | | | | sbuf_new_for_sysctl(9). This allows using an sbuf with a SYSCTL_OUT drain for extremely large amounts of data where the caller knows that appropriate references are held, and sleeping is not an issue. Inspired by: rwatson
* Remove the CTLFLAG_NOLOCK as it seems to be both unused andmdf2011-01-263-11/+8
| | | | | | | | | | | | unfunctional. Wiring the user buffer has only been done explicitly since r101422. Mark the kern.disks sysctl as MPSAFE since it is and it seems to have been mis-using the NOLOCK flag. Partially break the KPI (but not the KBI) for the sysctl_req 'lock' field since this member should be private and the "REQ_LOCKED" state seems meaningless now.
* Document newly added tunables.yongari2011-01-261-1/+25
| | | | | | hw.re.intr_filter hw.re.msix_disable dev.re.%d.int_rx_mod
* * Use 300 ms as the default for RTO_MIN.tuexen2011-01-261-4/+3
| | | | | | | * Disable burst mitigation by default. * Remove unused constant. Discussed with rrs. MFC after: 3 months.
* Add support for RTL8105E PCIe Fast Ethernet controller. It seemsyongari2011-01-262-1/+8
| | | | | | | | | | | | | | the controller has a kind of embedded controller/memory and vendor applies a large set of magic code via undocumented PHY registers in device initialization stage. I guess it's a firmware image for the embedded controller in RTL8105E since the code is too big compared to other DSP fixups. However I have no idea what that magic code does and what's purpose of the embedded controller. Fortunately driver seems to still work without loading the firmware. While I'm here change device description of RTL810xE controller. H/W donated by: Realtek Semiconductor Corp.
* Add Realtek RTL8201E 10/100 PHY found in RTL8105E controller. Theyongari2011-01-262-0/+2
| | | | | | exact model name is not clear yet. All previous RTL8201 10/100 PHYs used 0x8201 in MII_PHYIDR2 which in turn makes model number 0x20 but this PHY used new model number 0x08.
* Do not use interrupt taskqueue on controllers with MSI/MSI-Xyongari2011-01-262-32/+185
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | capability. One of reason using interrupt taskqueue in re(4) was to reduce number of TX/RX interrupts under load because re(4) controllers have no good TX/RX interrupt moderation mechanism. Basic TX interrupt moderation is done by hardware for most controllers but RX interrupt moderation through undocumented register showed poor RX performance so it was disabled in r215025. Using taskqueue to handle RX interrupt greatly reduced number of interrupts but re(4) consumed all available CPU cycles to run the taskqueue under high TX/RX network load. This can happen even with RTL810x fast ethernet controller and I believe this is not acceptable for most systems. To mitigate the issue, use one-shot timer register to moderate RX interrupts. The timer register provides programmable one-shot timer and can be used to suppress interrupt generation. The timer runs at 125MHZ on PCIe controllers so the minimum time allowed for the timer is 8ns. Data sheet says the register is 32 bits but experimentation shows only lower 13 bits are valid so maximum time that can be programmed is 65.528us. This yields theoretical maximum number of RX interrupts that could be generated per second is about 15260. Combined with TX completion interrupts re(4) shall generate less than 20k interrupts. This number is still slightly high compared to other intelligent ethernet controllers but system is very responsive even under high network load. Introduce sysctl variable dev.re.%d.int_rx_mod that controls amount of time to delay RX interrupt processing in units of us. Value 0 completely disables RX interrupt moderation. To provide old behavior for controllers that have MSI/MSI-X capability, introduce a new tunable hw.re.intr_filter. If the tunable is set to non-zero value, driver will use interrupt taskqueue. The default value of the tunable is 0. This tunable has no effect on controllers that has no MSI/MSI-X capability or if MSI/MSI-X is explicitly disabled by administrator. While I'm here cleanup interrupt setup/teardown since re(4) uses single MSI/MSI-X message at this moment.
* Add macro to test the sv_flags of any process. Change some places to testdchagin2011-01-2613-25/+27
| | | | | | | the flags instead of explicit comparing with address of known sysentvec structures. MFC after: 1 month
* Make SCTP_MAX_BURST compliant with the latest version oftuexen2011-01-261-13/+22
| | | | | the socket API ID. This is not compatible with the API in stable/8.
* Change infrastructure for SCTP_MAX_BURST to allow compliancetuexen2011-01-266-33/+43
| | | | | | | | | | with the latest socket API ID. Especially it can be disabled. Full compliance needs changing the structure used in the socket option. Since this breaks the API, it will be a seperate commit which will not be MFCed to stable/8. MFC after: 3 months.
* Unroll vgrind filter to no longer depend on vgrind(1) during buildworld.uqs2011-01-264-12/+1316
| | | | | The source files haven't been touched in ages and this is unlikely to change in the future.
* Fix typo in example getopt(1) script: $i vs $1 [1]uqs2011-01-261-17/+17
| | | | | | | | While here apply style hammer. PR: docs/154289 [1] Submitted by: Jamie Landeg Jones <jamie@bishopston.net> MFC after: 1 week
* Prison check addresses set with multicast interface options.deischen2011-01-261-6/+9
| | | | | Reviewed by: bz MFC after: 1 week
* Set td_kstack_pages for thread0. This was already being done for mostmdf2011-01-262-12/+18
| | | | | | architectures, but i386 and amd64 were missing it. Submitted by: Mohd Fahadullah <mfahadullah AT isilon DOT com>
* Add missing part of r217877.mav2011-01-261-0/+1
|
* Add ar5416RestoreChainMask() which will undo any AR5416 specific chainmaskadrian2011-01-262-0/+15
| | | | | | | overriding after calibration. This will get set for other two chain radios, such as AR9280 and later on, AR9287. It should however be a nul operation.
* Add an AR5416 workaround - force a different bias based on 2.4ghz channel ↵adrian2011-01-262-0/+67
| | | | | | frequency. Obtained from: Linux ath9k
* Treat async buffer writes from the gjournal switcher thread the same askib2011-01-261-0/+1
| | | | | | | | from syncer. We shall not sleep on running buffer space when suspending. Reproduced and tested by: pho PR: kern/154228 MFC after: 1 week
* Break out the chainmask init code into a new function - ar5416InitChainMasks() .adrian2011-01-262-8/+18
| | | | | | | | | | | ath9k does a few different things here during config - if it's an early AR5416 with two chains, it enables all three chains for calibration and then restores the chainmask to the original values after initial calibration has completed. The reason behind this commit is to begin breaking out the chainmask configuration for this specific reason; follow-up commits will add the chainmask restore in the ar5416Reset() routine.
* * fix HAL_DEBUG_INTERRUPT to be a separate bit, it was overlapping withadrian2011-01-261-1/+2
| | | | | | something else * add HAL_DEBUG_GPIO, for some GPIO related debugging I'm tinkering with at the moment.
* Hardware supported by siis(4) allows software control over activity LEDs.mav2011-01-261-0/+19
| | | | Expose that functionality to led(4) OR-ing it with regular LED activity.
* In addition to r217444 ignore also ATA status errors on DMA Auto-Activationmav2011-01-261-0/+8
| | | | | enabling request. Some HP disks reported to return ABORT error there while declaring support for this feature.
* Make device initialization sequence shorter when possible. Do not enable/mav2011-01-261-3/+9
| | | | disable already enabled/disabled SATA features.
OpenPOWER on IntegriCloud