summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge OpenSSL 1.0.1e.jkim2013-02-13510-1602/+3405
|\ | | | | | | Approved by: secteam (simon), benl (silence)
| * Import OpenSSL 1.0.1e.jkim2013-02-13175-874/+2672
| | | | | | | | Approved by: secteam (delphij, simon), benl (silence)
| * Integrate OpenSSL changeset 22950 (appro):delphij2013-01-021-17/+8
| | | | | | | | bn_word.c: fix overflow bug in BN_add_word.
* | Change "the the" to "the". It is a continuation of r226436 and missed injkim2013-02-131-1/+1
| | | | | | | | | | | | r237658. Approved by: benl (maintainer, implicit)
* | Restore De Bruijn algorithm for sparc64 where the compiler rely on adelphij2013-02-131-0/+63
| | | | | | | | | | | | library function for __builtin_c?z. Tested by: Michael Moll <kvedulv kvedulv de>
* | Add strchrnul(), a GNU function similar to strchr(), except that it returnszeising2013-02-135-5/+84
| | | | | | | | | | | | | | a pointer to the end of the string, rather than NULL, if the character was not found. Approved by: theraven
* | Remove unused variable.hselasky2013-02-132-2/+0
| | | | | | | | MFC after: 1 week
* | Add a dependency so that when compiling in a static dtb, the kernel getsian2013-02-131-1/+2
| | | | | | | | | | | | re-linked after changing the .dts source. Reviewed by: cognet, arm@
* | Make the F_READAHEAD option to fcntl(2) work as documented: a value of zeroian2013-02-132-3/+3
| | | | | | | | | | | | | | | | now disables read-ahead. It used to effectively restore the system default readahead hueristic if it had been changed; a negative value now restores the default. Reviewed by: kib
* | Resolve a LOR after r246616. Protect control requests using the USB devicehselasky2013-02-139-43/+55
| | | | | | | | | | | | | | | | | | enumeration lock. Make sure all callers of usbd_enum_lock() check the return value. Remove the control transfer specific lock. Bump the FreeBSD version number, hence external USB modules may need to be recompiled due to a USB device structure change. MFC after: 1 week
* | Add new USB ID to FTDI driver.hselasky2013-02-132-0/+2
| | | | | | | | | | | | MFC after: 1 week PR: kern/175893 Submitted by: Tomek
* | Add specific supported revision of D-Link DWA-140 rev B1, B2.hselasky2013-02-131-1/+1
| | | | | | | | | | Submitted by: PseudoCylon MFC after: 1 week
* | Fix my email.glebius2013-02-131-1/+1
| |
* | Add myself as a ports committer and my mentor relationship.pclin2013-02-131-0/+4
| | | | | | | | Approved by: swills (mentor)
* | Pull out the if_transmit() work and revert back to ath_start().adrian2013-02-134-451/+107
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | My changed had some rather significant behavioural changes to throughput. The two issues I noticed: * With if_start and the ifnet mbuf queue, any temporary latency would get eaten up by some mbufs being queued. With ath_transmit() queuing things to ath_buf's, I'd only get 512 TX buffers before I couldn't queue any further frames. * There's also some non-zero latency involved with TX being pushed into a taskqueue via direct dispatch. Any time the scheduler didn't immediately schedule the ath TX task would cause extra latency. Various 1ge/10ge drivers implement both direct dispatch (if the TX lock can be acquired) and deferred task transmission (if the TX lock can't be acquired), with frames being pushed into a drbd queue. I'll have to do this at some point, but until I figure out how to deal with 802.11 fragments, I'll have to wait a while longer. So what I saw: * lots of extra latency, specially under load - if the taskqueue wasn't immediately scheduled, things went pear shaped; * any extra latency would result in TX ath_buf's taking their sweet time being replenished, so any further calls to ath_transmit() would drop mbufs. * .. yes, there's no explicit backpressure here - things are just dropped. Eek. With this, the general performance has gone up, but those subtle if_start() related race conditions are back. For some reason, this is doubly-obvious with the AR5416 NIC and I don't quite understand why yet. There's an unrelated issue with AR5416 performance in STA mode (it's fine in AP mode when bridging frames, weirdly..) that requires a little further investigation. Specifically - it works fine on a Lenovo T40 (single core CPU) running a March 2012 9-STABLE kernel, but a Lenovo T60 (dual core) running an early November 2012 kernel behaves very poorly. The same hardware with an AR9160 or AR9280 behaves perfectly.
* | Introduce PLATFORMMETHOD_END and use it.rpaulo2013-02-135-5/+6
| |
* | - Make actually printing path of AF_LOCAL socket types.zont2013-02-121-3/+1
| | | | | | | | MFC after: 1 week
* | - Use correct size of copying different socket structures.zont2013-02-121-5/+5
| | | | | | | | MFC after: 1 week
* | Eliminate the PC_CURTHREAD symbol and load the current thread'smarcel2013-02-123-35/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | thread structure pointer atomically from r13 (the pcpu pointer) for the current CPU/core. Add a CTASSERT in machdep.c to make sure that pc_curthread is in fact the first field in struct pcpu. The only non-atomic operations left were those related to process- space operations, such as casuword, subyte, suword16, fubyte, fuword16, copyin, copyout and their variations. The casuword function has been re-structured more complete than the others. This way we have an example of a better bundling without introducing a lot of risk when we get it wrong. The other functions can be rebundled in separate commits and with the appropriate testing.
* | Eliminate padding by moving 'narg' next to 'code'. Both are 32-bitmarcel2013-02-121-1/+1
| | | | | | | | | | entities in the syscall_args structure that otherwise has 64-bit only fields.
* | Reform the busdma API so that new types may be added without modifyingkib2013-02-1268-3733/+3074
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | every architecture's busdma_machdep.c. It is done by unifying the bus_dmamap_load_buffer() routines so that they may be called from MI code. The MD busdma is then given a chance to do any final processing in the complete() callback. The cam changes unify the bus_dmamap_load* handling in cam drivers. The arm and mips implementations are updated to track virtual addresses for sync(). Previously this was done in a type specific way. Now it is done in a generic way by recording the list of virtuals in the map. Submitted by: jeff (sponsored by EMC/Isilon) Reviewed by: kan (previous version), scottl, mjacob (isp(4), no objections for target mode changes) Discussed with: ian (arm changes) Tested by: marius (sparc64), mips (jmallet), isci(4) on x86 (jharris), amd64 (Fabian Keil <freebsd-listen@fabiankeil.de>)
* | Now that we actually use more memory descriptors, make sure to dumpmarcel2013-02-121-1/+4
| | | | | | | | them as well.
* | o Bring in sync decoding the first nfssvc(2) parameter (flags) withpluknet2013-02-121-1/+1
| | | | | | | | | | | | | | the current definitions location. o Respect numbers in NFSSVC_* (e.g. NFSSVC_V4ROOTEXPORT). MFC after: 1 week
* | Substitute '#ifdef ALIGNED_POINTER' with '#ifndef __NO_STRICT_ALIGNMENT',glebius2013-02-123-4/+6
| | | | | | | | | | | | | | | | since the former is defined everywhere. This cuts off some code not necessary on non strict aligment arches. Reviewed by: adrian Sponsored by: Nginx, Inc.
* | Remove debug outputgonzo2013-02-121-1/+0
| |
* | When clang builds libc it may insert calls to __aeabi_* functions. Normallyandrew2013-02-121-0/+19
| | | | | | | | | | | | | | | | | | | | this is not a problem as they are resolved by libgcc. The exception is for the __aeabi_mem* functions. These call back into libc to the appropriate function. This causes issues for static binaries as we only link against libc once so there is no way for it to call into libgcc and back. The fix for this is to include these symbols in libc but keep them hidden so binaries use the libgcc version.
* | Allow us to build clang for ARM EABI. Clang and llvm use theandrew2013-02-1221-6/+54
| | | | | | | | | | | | | | arm-gnueabi-freebsd10.0 triple for EABI. Use this when we are on arm or armv6 and are building for EABI. Reviewed by: dim
* | Style.pjd2013-02-111-2/+2
| |
* | Update comments to reflect r246689.marius2013-02-111-2/+8
| |
* | Style.pjd2013-02-111-2/+2
| |
* | Make SYSCTL_{LONG,QUAD,ULONG,UQUAD}(9) work as advertised and also handlemarius2013-02-111-9/+17
| | | | | | | | | | | | | | constant values. Reviewed by: kib MFC after: 3 days
* | Merge zfs_ioctl.c code that should have been merged together with ZFS v28.mm2013-02-111-75/+100
| | | | | | | | | | | | | | | | | | | | | | | | Fixes several problems if working with read-only pools. Changed code originaly introduced in onnv-gate 13061:bda0decf867b Contains changes up to illumos-gate 13700:4bc0783f6064 PR: kern/175897 Suggested by: avg MFC after: 2 weeks
* | Send the adaptation layer indication only if set by the user.tuexen2013-02-114-19/+26
| | | | | | | | | | MFC after: 3 days Discussed with: rrs
* | Implement guest vcpu pinning using 'pthread_setaffinity_np(3)'.neel2013-02-119-165/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Prior to this change pinning was implemented via an ioctl (VM_SET_PINNING) that called 'sched_bind()' on behalf of the user thread. The ULE implementation of 'sched_bind()' bumps up 'td_pinned' which in turn runs afoul of the assertion '(td_pinned == 0)' in userret(). Using the cpuset affinity to implement pinning of the vcpu threads works with both 4BSD and ULE schedulers and has the happy side-effect of getting rid of a bunch of code in vmm.ko. Discussed with: grehan
* | Use the right year.delphij2013-02-112-2/+2
| | | | | | | | Noticed by: Denis Ahrens <denis h3q com>
* | MFV r246633:mm2013-02-111-1/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Import vendor bugfixes regarding SA rounding, header size and layout. This was already partially fixed by avg. Illumos ZFS issues: 3512 rounding discrepancy in sa_find_sizes() 3513 mismatch between SA header size and layout References: https://www.illumos.org/issues/3512 https://www.illumos.org/issues/3513 MFC after: 2 weeks
* | MFV r246394:mm2013-02-111-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | Add tunable to allow block allocation on degraded vdevs. Illumos ZFS issues: 3507 Tunable to allow block allocation even on degraded vdevs References: https://www.illumos.org/issues/3507 MFC after: 2 weeks
* | Don't send kernel provided information in the User Initiatedtuexen2013-02-114-68/+29
| | | | | | | | | | | | | | | | | | | | | | ABORT cause, since the user can also provide this kind of information. So the receiver doesn't know who provided the information. While there: Fix a bug where the stack would send a malformed ABORT chunk when using a send() call with SCTP_ABORT|SCT_SENDALL flags. MFC after: 3 days
* | Major update for unix_cmsg from Andrey Simonenko.pluknet2013-02-113-1249/+1652
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Quoting the submitter: - Added tests for SCM_BINTIME, LOCAL_PEERCRED, cmsghdr.cmsg_len - Code that checks correctness of groups was corrected (getgroups(2) change) - unix_cmsg.c was completely redesigned and simplified - Use less timeout value in unix_cmsg.c for faster work - Added support for not sending data in a message, not sending data and data array associated with a cmsghdr structure in a message - Existent tests were improved - unix_cmsg.t was redesigned and simplified Correctness of unix_cmsg verified on 7.1-STABLE, 9.1-STABLE and 10-CURRENT. PR: bin/131567 Submitted by: Andrey Simonenko <simon@comsys.ntu-kpi.kiev.ua> MFC after: 2 weeks
* | MFV r246392:mm2013-02-1117-197/+76
| | | | | | | | | | | | | | | | | | | | | | | | Import vendor ZFS bugfix fixing a possible deadlock in arc_read(). Illumos ZFS issues: 3498 panic in arc_read(): !refcount_is_zero(&pbuf->b_hdr->b_refcnt) References: https://www.illumos.org/issues/3498 MFC after: 2 weeks
* | A10 reset mechanism is the same for all boards in this family so removegonzo2013-02-111-6/+3
| | | | | | | | | | redundant reset function implementation pointer. We might want to ressurect it later when support for other Allwinner chips is introduced.
* | Add watchdog driver for Allwinner A10gonzo2013-02-114-0/+236
| |
* | Resolve source address selection in presense of CARP. Add a coupleglebius2013-02-114-4/+34
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | of helper functions: - carp_master() - boolean function which is true if an address is in the MASTER state. - ifa_preferred() - boolean function that compares two addresses, and is aware of CARP. Utilize ifa_preferred() in ifa_ifwithnet(). The previous version of patch also changed source address selection logic in jails using carp_master(), but we failed to negotiate this part with Bjoern. May be we will approach this problem again later. Reported & tested by: Anton Yuzhaninov <citrin citrin.ru> Sponsored by: Nginx, Inc
* | Cross-reference vfs_unbusy(9).pluknet2013-02-111-1/+3
| | | | | | | | MFC after: 1 week
* | Add -lheimntlm to LDADD directly.brooks2013-02-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | With the current binutils, symbols from libheimtlm.so are loaded because it is referenced by DT_NEEDED. This feature is not implemented in mclinker (https://code.google.com/p/mclinker/issues/detail?id=104). I encountered the same issue when linking with a recent devel/binutils invoked via clang. This was the only use of DT_NEEDED in the tree so removing it simplifies toolchain requirements. Submitted by: Pete Chou <petechou@gmail.com> (mclinker issue)
* | Use DEVMETHOD_END.rpaulo2013-02-113-3/+3
| |
* | Put this back into the ath taskqueue rather than the ath TX taskqueue.adrian2013-02-111-1/+1
| | | | | | | | | | This now should mean all the entry points into the software TX scheduler are back in the same taskqueue.
* | MFV r246390:mm2013-02-111-2/+3
| | | | | | | | | | | | Import minor type change in refcount.h header from vendor (illumos). MFC after: 2 weeks
* | Go back to direct-dispatch of the software queue and frame TX pathsadrian2013-02-111-7/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | when they're being called from the TX completion handler. Going (back) through the taskqueue is just adding extra locking and latency to packet operations. This improves performance a little bit on most NICs. It still hasn't restored the original performance of the AR5416 NIC but the AR9160, AR9280 and later NICs behave very well with this. Tested: * AR5416 STA (still tops out at ~ 70mbit TCP, rather than 150mbit TCP..) * AR9160 hostap (good for both TX and RX) * AR9280 hostap (good for both TX and RX)
* | Teach athalq about the recent if_ath_alq timestamp format change.adrian2013-02-115-34/+51
| |
OpenPOWER on IntegriCloud