summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* * Add a rather hacky "does this speak the 11n TX descriptor format"adrian2011-02-011-94/+86
| | | | | | | | | | | | function; which will be later used by the TX path to determine whether to use the extended features or not. * Break out the descriptor chaining logic into a separate function; again so it can be switched out later on for the 11n version when needed. * Refactor out the encryption-swizzling code that's common in the raw and normal TX path.
* Import a clean-room implementation of the Hamilton-Delay (HD) congestion controllstewart2011-02-013-0/+264
| | | | | | | | | | | | | | | | | | | | | | algorithm based on the paper "A strategy for fair coexistence of loss and delay-based congestion control algorithms" by Budzisz, Stanojevic, Shorten and Baker. It is implemented as a kernel module compatible with the recently committed modular congestion control framework. HD uses a probabilistic approach to reacting to delay-based congestion. The probability of reducing cwnd is zero when the queuing delay is very small, increasing to a maximum at a set threshold, then back down to zero again when the queuing delay is high. Normal operation keeps the queuing delay below the set threshold. However, since loss-based congestion control algorithms push the queuing delay high when probing for bandwidth, having the probability of reducing cwnd drop back to zero for high delays allows HD to compete with loss-based algorithms. In collaboration with: David Hayes <dahayes at swin edu au> and Grenville Armitage <garmitage at swin edu au> Sponsored by: FreeBSD Foundation Reviewed by: bz and others along the way MFC after: 3 months
* Import a clean-room implementation of the VEGAS congestion control algorithmlstewart2011-02-013-1/+319
| | | | | | | | | | | | | | | | | based on the paper "TCP Vegas: end to end congestion avoidance on a global internet" by Brakmo and Peterson. It is implemented as a kernel module compatible with the recently committed modular congestion control framework. VEGAS uses network delay as a congestion indicator and unlike regular loss-based algorithms, attempts to keep the network operating with stable queuing delays and no congestion losses. By keeping network buffers used along the path within a set range, queuing delays are kept low while maintaining high throughput. In collaboration with: David Hayes <dahayes at swin edu au> and Grenville Armitage <garmitage at swin edu au> Sponsored by: FreeBSD Foundation Reviewed by: bz and others along the way MFC after: 3 months
* Add TX/RX chainmask info to if_ath - this is needed for the 11n TX rate series.adrian2011-02-011-0/+6
|
* Add a new capability which reports the number of spatial streams a device ↵adrian2011-02-017-0/+29
| | | | | | | | | | | | | | | | supports. The higher levels (net80211, if_ath, ath_rate) need this to make correct choices about what MCS capabilities to advertise and what MCS rates are able to be TXed. In summary: * AR5416 - 2/3 antennas, 2x2 streams * AR9160 - 2/3 antennas, 2x2 streams * AR9220 - 2 antennas, 2x2 sstraems * AR9280 - 2 antennas, 2x2 streams * AR9285 - 2 antennas but with antenna diversity, 1x1 stream
* Support for the new Patsburg PCH chipset:jfv2011-02-017-3/+29
| | | | | | | | | | | - SMBus Controller - SATA Controller - HD Audio Controller - Watchdog Controller Thanks to Seth Heasley (seth.heasley@intel.com) for providing us code. MFC after 3 days
* Fix build on ia64.pjd2011-01-311-9/+7
| | | | | | | I found no way how to use CMSG_NXTHDR() macro on ia64 without alignment warnings. MFC after: 1 week
* Until I fix the build on ia64 comment out problematic lines.pjd2011-01-311-2/+2
| | | | Those lines are part of the (for now) unused functions.
* Remove the now unneeded XXX.adrian2011-01-311-1/+0
|
* Enable AMPDU reorder processing and receiving BAR frames when doing 802.11n.adrian2011-01-311-0/+6
| | | | Obtained from: rpaulo@
* Let rpcbind clean up after itselfdougb2011-01-311-0/+2
|
* alc_rev was used without initialization such that it failed toyongari2011-01-311-1/+1
| | | | | | | apply AR8152 v1.0 specific initialization code. Fix this bug by explicitly reading PCI device revision id via PCI accessor. Reported by: Gabriel Linder ( linder.gabriel <> gmail dot com )
* Support for the new DH89xxCC PCH chipset including:jfv2011-01-316-0/+9
| | | | | | - SATA controller - Watchdog timer - SMBus controller
* Implement two new functions for sending descriptor and receving descriptorpjd2011-01-316-8/+173
| | | | | | | over UNIX domain sockets and socket pairs. This is in preparation for capsicum. MFC after: 1 week
* - Use pjdlog for assertions and aborts as this will log assert/abort messagepjd2011-01-319-241/+197
| | | | | | | | | to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week
* Rename pjdlog_verify() to pjdlog_abort() as it better describes what thepjd2011-01-312-7/+7
| | | | | | the function does and mark it with __dead2. MFC after: 1 week
* Don't incorrectly set the burst duration setting in the TX descriptor.adrian2011-01-311-2/+0
| | | | | | | | | | | | | | | | After inspecting the ath9k source, it seems the AR5416 and later MACs don't take an explicit RTS/CTS duration. A per-scenario (ie, what multi- rate retry became) rts/cts control flag and packet duration is provided; the hardware then apparently fills in whatever details are required. The per-rate sp/lpack duration calculation just isn't used anywhere in the ath9k TX packet length calculations. The burst duration register controls something different; it seems to be involved with RTS/CTS protection of 11n aggregate frames and is set via a call to ar5416Set11nBurstDuration(). I've done some light testing with rts/cts protected frames and nothing seems to break; but this may break said RTS/CTS and CTS-to-self protection.
* Move the architecture guessing from Makefile.inc1 to Makefile. Weimp2011-01-312-28/+33
| | | | | | | | | | need to do this because variables specified on the command line override those specified in the Makefile. This is why we also moved from TARGET to _TARGET in Makefile, and then set TARGET on the command line when we fork a submake with Makefile.inc1. This makes mips/mips work again, even without the workaround committed to lib/libc/Makefile.
* More ECN fixes:rrs2011-01-3113-486/+86
| | | | | | | | | | | 1) We now remove ECN-Nonce since it will no longer continue as a I-D 2) Eliminate last_tsn_echo, this tied us to an assoc not the net and thus we were not doing m-homing on the ECN-Echo senders side right. 3) Increment the count going out even if the TSN in lower in the pending ECN-Echo, this way the receiver knows exactly how many packets were marked even with network re-ordering 4) Fix so we DO NOT stop doing delayed sack if a ECN Echo is in queue MFC after: 1 month
* Use correct alphabetical order for xz(1) in SEE ALSO sectionmm2011-01-312-2/+2
| | | | | | | of newsyslog manpages. Reported by: maxim MFC after: 3 weeks
* Add xz(1) support to newsyslog.mm2011-01-314-99/+136
| | | | | | | Rewrite and simplify logfile compression code. Approved by: gad MFC after: 3 weeks
* MFV of tzdata2011a, r218120edwin2011-01-312-23/+52
| | | | | - Cleanup rules for Australia/South_Australia (nothing changed) - Add historical information for Honolulu.
* o Add user 'hast'.maxim2011-01-312-0/+2
|
* Yet another unimplemented futex operation, print out about.dchagin2011-01-312-0/+8
| | | | | Submitted by: arundel MFC after: 1 month.
* Implement a futex BITSET op.dchagin2011-01-312-25/+46
| | | | | Submitted by: arundel MFC after: 1 month.
* Update interface stats counters to match the current format in linux andbz2011-01-311-8/+31
| | | | | | | | try to export as much information as we can match. Requested on: Debian GNU/kFreeBSD list (debian-bsd lists.debian.org) 2010-12 Tested by: Mats Erik Andersson (mats.andersson gisladisker.se) MFC after: 10 days
* Release the free page queues lock earlier in vm_page_alloc().alc2011-01-301-2/+7
| | | | Discussed with: kib@
* sh: Send messages about signals to stderr.jilles2011-01-302-5/+15
| | | | | | This is required by POSIX and seems to make more sense. See also r217557.
* Regen for r218101.dchagin2011-01-302-6/+6
| | | | MFC after: 1 Month.
* Change linux futex syscall definition to match actual linux one.dchagin2011-01-302-4/+4
| | | | MFC after: 1 Month.
* The kern_wait() code already removes the SIGCHLD signal for the waiteddchagin2011-01-302-14/+0
| | | | | | | | | process. Removing other SIGCHLD signals is not needed and may cause problems. Pointed out by: jilles MFC after: 1 Month.
* Fix grammar in comment.kib2011-01-301-1/+1
| | | | | Pointy hat to: kib MFC after: 1 week
* Make ldd(1) work when versioned dependency file is cannot be loaded.kib2011-01-301-4/+13
| | | | | | | | | | Instead of aborting in locate_dependency(), propagate the error to caller. The rtld startup function does the right thing with an error from rtld_verify_versions(), depending on the mode of operation. Reported by: maho In collaboration with: kan MFC after: 1 week
* Fix the 'scan hang' issue.bschmidt2011-01-301-2/+6
| | | | | | | | | | | | When requesting a scan and one is already in progess, e.g. while in scan state, we happily wait for a scan done notification. Though, this notification might never be sent, e.g. if we are trying to find a network to associate to and there is none. Instead of always waiting for a notification just do so if a new scan has been started. For both cases the scan cache is used to report available networks even if the content might not be fresh. MFC after: 1 month
* Instead of always returning 0 to a scan request, indicate if there isbschmidt2011-01-301-4/+5
| | | | | | one running already. MFC after: 1 month
* Change return code semantics of start_scan_locked(). Instead of reportingbschmidt2011-01-301-1/+2
| | | | | | | | if a scan is running, report if a scan has been started. The return value itself is not (yet) used anywhere in the tree and it is also not exported to userspace. MFC after: 1 month
* When doing a scan while being associated it is possible that the scanbschmidt2011-01-301-0/+1
| | | | | | | | | | | | is deferred for the time it takes to flush the TX queue. This work being done the scan then is continued, but only if it is marked to do so. As the 'ifconfig scan' request is meant to be used after the interface is brought up, request a background scan by default. This behaviour is already documented in manual page. This fixes on possible case where 'ifconfig scan' hangs infinitely. MFC after: 1 month
* syscons: install all available kbdmapsuqs2011-01-301-3/+3
| | | | | | | eee_nordic.kbd, us.dvorakl.kbd, and us.dvorakr.kbd were not installed. Found by: Neil Short <neshort@yahoo.com> MFC after: 3 weeks
* Add support for the m25p64; lifted straight from Linux.adrian2011-01-301-0/+1
| | | | | This flash chip is found on the Ubiquiti LS-SR71 board. I've successfully tested reading; I've not tried writing to it yet.
* Honor the IEEE80211_SCAN_BGSCAN flag, which makes it possible to actuallybschmidt2011-01-301-0/+2
| | | | | | request a background scan using IEEE80211_IOC_SCAN_BGSCAN. MFC after: 1 month
* Fix boot on SMP systems after r218075 by delaying CPU binding until anwhitehorn2011-01-291-3/+0
| | | | | | SYSINIT. Reviewed by: marcel
* Remove duplicate printing of TF_NOPUSH in db_print_tflags().bz2011-01-291-4/+0
| | | | MFC after: 10 days
* Don't operate on the parent of the PCI node. It's the PCI node itselfmarcel2011-01-291-32/+234
| | | | | | | | | | | | | | | that represents the host controller. This makes the FDT PCI support working an a bare-bones manner. This needs a lot more work, of which the beginning are at the end of the file, compiled-out with #if 0. The intend being that both the Marvell PCIE and Freescale PCI/PCIX/PCIE duplicate the same platform-independent domain initialization, that should be moved into an unified implementation in the FDT code. Handling of resources requires help from the platform. A unified implementation allows us to properly support PCI devices listed in the device tree and configured according to the device tree specification. Sponsored by: Juniper Networks
* Call newbus_device_create() for PCI devices. Call pci_from_fdt_node()marcel2011-01-291-7/+8
| | | | for the newly created device_t, rather than the parent.
* Fix the interrupt code, broken 7 months ago. The interrupt frameworkmarcel2011-01-2915-202/+162
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | already supported nested PICs, but was limited to having a nested AT-PIC only. With G5 support the need for nested OpenPIC controllers needed to be added. This was done the wrong way and broke the MPC8555 eval system in the process. OFW, as well as FDT, describe the interrupt routing in terms of a controller and an interrupt pin on it. This needs to be mapped to a flat and global resource: the IRQ. The IRQ is the same as the PCI intline and as such needs to be representable in 8 bits. Secondly, ISA support pretty much dictates that IRQ 0-15 should be reserved for ISA interrupts, because of the internal workins of south bridges. Both were broken. This change reverts revision 209298 for a big part and re-implements it simpler. In particular: o The id() method of the PIC I/F is removed again. It's not needed. o The openpic_attach() function has been changed to take the OFW or FDT phandle of the controller as a second argument. All bus attachments that previously used openpic_attach() as the attach method of the device I/F now implement as bus-specific method and pass the phandle_t to the renamed openpic_attach(). o Change powerpc_register_pic() to take a few more arguments. In particular: - Pass the number of IPIs specificly. The number of IRQs carved out for a PIC is the sum of the number of int. pins and IPIs. - Pass a flag indicating whether the PIC is an AT-PIC or not. This tells the interrupt framework whether to assign IRQ 0-15 or some other range. o Until we implement proper multi-pass bus enumeration, we have to handle the case where we need to map from PIC+pin to IRQ *before* the PIC gets registered. This is done in a similar way as before, but rather than carving out 256 IRQs per PIC, we carve out 128 IRQs (124 pins + 4 IPIs). This is supposed to handle the G5 case, but should really be fixed properly using multiple passes. o Have the interrupt framework set root_pic in most cases and not put that burden in PIC drivers (for the most part). o Remove powerpc_ign_lookup() and replace it with powerpc_get_irq(). Remove IGN_SHIFT, INTR_INTLINE and INTR_IGN. Related to the above, fix the Freescale PCI controller driver, broken by the FDT code. Besides not attaching properly, bus numbers were assigned improperly and enumeration was broken in general. This prevented the AT PIC from being discovered and interrupt routing to work properly. Consequently, the ata(4) controller stopped functioning. Fix the driver, and FDT PCI support, enough to get the MPC8555CDS going again. The FDT PCI code needs a whole lot more work. No breakages are expected, but lackiong G5 hardware, it's possible that there are unpleasant side-effects. At least MPC85xx support is back to where it was 7 months ago -- it's amazing how badly support can be broken in just 7 months... Sponsored by: Juniper Networks
* Have nexus behave the same as the one on ARM (marvell SoCs), so as tomarcel2011-01-291-8/+17
| | | | prevent warnings during boot WRT to the fdtbus attachment.
* Introduce macro FDT_MAP_IRQ to map from an interrupt controller andmarcel2011-01-293-2/+9
| | | | | interrupt pin pair to a global IRQ number. When multiple PICs exist on a board, the interrupt pin alone is not unique.
* Fixes to ECN in SCTP.rrs2011-01-299-53/+165
| | | | | | | | | | | | | 1) ECN was on an association basis, this is incorrect and will not work with CMT or for that matter if the user is sending to multiple addresses. This commit makes ECN on a per path basis. 2) Adopt the new format for the ECN internet draft. This also maintains compatability with old format chunks as well. 3) Keep track of the real time of a RTT down to micro seconds. For some future conditional features (for like a data center this is good information to have). MFC after: 1 month
* Reenable the call to vm_map_simplify_entry() from vm_map_insert() for non-alc2011-01-291-9/+5
| | | | | | | MAP_STACK_* entries. (See r71983 and r74235.) In some cases, performing this call to vm_map_simplify_entry() halves the number of vm map entries used by the Sun JDK.
* Avoid writing CCA threshold values for the EXT radios for non-HT40 channels.adrian2011-01-291-0/+6
|
OpenPOWER on IntegriCloud