summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Explicitly abort a timed out command, if the ABORT command sent to thejimharris2013-03-261-1/+29
| | | | | | controller indicates the command was not found. Sponsored by: Intel
* Break out the code for completing an nvme_tracker object into a separatejimharris2013-03-261-43/+59
| | | | | | | | | | | function. This allows for completions outside the normal completion path, for example when an ABORT command fails due to the controller reporting the targeted command does not exist. This is mainly for protection against a faulty controller, but we need to clean up our internal request nonetheless. Sponsored by: Intel
* Add support for ABORT commands, including issuing these commands whenjimharris2013-03-263-5/+24
| | | | | | | | an I/O times out. Also ensure that we retry commands that are aborted due to a timeout. Sponsored by: Intel
* Add an internal _nvme_qpair_submit_request function, which performsjimharris2013-03-261-6/+15
| | | | | | | | | | | the submit action assuming the qpair lock has already been acquired. Also change nvme_qpair_submit_request to just lock/unlock the mutex around a call to this new function. This fixes a recursive mutex acquisition in the retry path. Sponsored by: Intel
* Make the DSM range count 0-based. Previously we were deallocating one morejimharris2013-03-261-1/+1
| | | | | | LBA than we should have been. Sponsored by: Intel
* Do not look at the namespace's thin provisioning field to determine if DSMjimharris2013-03-261-1/+1
| | | | | | command is supported. The two are not related. Sponsored by: Intel
* Introduce vm_radix_isleaf() and use it in a couple places. As compared toalc2013-03-261-2/+12
| | | | | | | | | | using vm_radix_node_page() == NULL, the compiler is able to generate one less conditional branch when vm_radix_isleaf() is used. More use cases involving the inner loops of vm_radix_insert(), vm_radix_lookup{,_ge,_le}(), and vm_radix_remove() will follow. Reviewed by: attilio Sponsored by: EMC / Isilon Storage Division
* Return ENOMEM if malloc() fails.glebius2013-03-261-1/+1
|
* Cleanup: wrap long lines, cleanup comments, etc.glebius2013-03-262-113/+141
|
* geom_slice.c and its consumers like GEOM_LABEL are not touching the datamav2013-03-261-0/+8
| | | | | unless hotspots are used. Pass G_PF_ACCEPT_UNMAPPED flag through except such rare cases (obsolete GEOM_SUNLABEL and GEOM_BSD).
* GEOM NOP does not touch the data, so pass G_PF_ACCEPT_UNMAPPED flag through.mav2013-03-261-0/+1
|
* Remove extra bio_data and bio_length copying to child request after callingmav2013-03-263-6/+0
| | | | g_clone_bio(), that already copied them.
* Remove the mcast path calls to ath_hal_gettxdesclinkptr() for axq_link -adrian2013-03-262-3/+0
| | | | | | | | | | they're no longer needed for the legacy path and they're not wanted for the EDMA path. Tested: * AR9280, hostap + CABQ * AR9380/AR9580, hostap + CABQ
* Remove this dead code - it's no longer relevant (as yes, we do actuallyadrian2013-03-261-8/+0
| | | | support TX on EDMA chips.)
* Convert the CABQ queue code over to use the HAL link pointer methodadrian2013-03-261-8/+15
| | | | | | | | | | | | | | | | | | | | instead of axq_link. This (among a bunch of uncommitted work) is required for EDMA chips to correctly transmit frames on the CABQ. Tested: * AR9280, hostap mode * AR9380/AR9580, hostap mode (staggered beacons) TODO: * This code only really gets called when burst beacons are used; it glues multiple CABQ queues together when sending to the hardware. * More thorough bursted beacon testing! (first requires some work with the beacon queue code for bursted beacons, as that currently uses the link pointer and will fail on EDMA chips.)
* Convert the EDMA multicast queue code over to use the HAL method to setadrian2013-03-261-3/+5
| | | | | | | | | | | the descriptor link pointer, rather than directly. This is needed on AR9380 and later (ie, EDMA) NICs so the multicast queue has a chance in hell of being put together right. Tested: * AR9380, AR9580 in hostap mode, CABQ traffic (but with other patches..)
* Migrate the multicast queue assembly code to not use the axq_link pointeradrian2013-03-261-5/+7
| | | | | | | | and instead use the HAL method to set the link pointer. Tested: * AR9280, hostap mode, CABQ frames being queued and transmitted
* Do not pass unmapped buffers to drivers that cannot handle themkan2013-03-263-3/+14
| | | | | | | | | | | | | | In physio, check if device can handle unmapped IO and pass an appropriately mapped buffer to the driver strategy routine. The only driver in the tree that can handle unmapped buffers is one exposed by GEOM, so mark it as such with the new flag in the driver cdevsw structure. This fixes insta-panics on hosts, running dconschat, as /dev/fwmem is an example of the driver that makes use of physio routine, but bypasses the g_down thread, where the buffer gets mapped normally. Discussed with: kib (earlier version)
*-. Dtrace: Add SUN MDB-like type-aware print() action.pfg2013-03-2523-74/+1254
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge change from illumos: 1694 Add type-aware print() action This is a very nice feature implemented in upstream Dtrace. A complete description is available here: http://dtrace.org/blogs/eschrock/2011/10/26/your-mdb-fell-into-my-dtrace/ This change bumps the DT_VERS_* number to 1.9.0 in accordance to what is done in illumos. While here also include some minor cleanups to ease further merging and appease clang with a fix by Fabian Keil. Illumos Revisions: 13501:c3a7090dbc16 13483:f413e6c5d297 Reference: https://www.illumos.org/issues/1560 https://www.illumos.org/issues/1694 Tested by: Fabian Keil Obtained from: Illumos MFC after: 1 month
| * | Merge r238587 into 20120614 tagmm2012-07-181-0/+533
| | |
* | | hrStorageSize and hrStorageUsed are 32 bit integers, reporting a fstrociny2013-03-251-19/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | size and usage in hrStorageAllocationUnits. If the file system has more than 2^31 allocations it can not be shown correctly and the meters are useless. In such cases follow net-snmp behaviour and increase hrStorageAllocationUnits so the values fit under INT_MAX. PR: bin/177183 Submitted by: Eugene Grosbein egrosbein rdtc.ru MFC after: 2 weeks
* | | Dtrace: add toupper()/tolower() and enhancements to lltostr().pfg2013-03-2513-16/+789
|\ \ \ | | |/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge changes from illumos: 1451 DTrace needs toupper()/tolower() subroutines 1457 lltostr() D subroutine should take an optional base This change bumps the DT_VERS_* number to 1.8.1 in accordance to what is done in illumos. The test suite we currently include is outdated and doesnt support some updates in tst.subr.d which had to be left out for now. Illumos Revisions: r13458 5e394d8db762 r13459 c3454574dd1a Reference: https://www.illumos.org/issues/1451 https://www.illumos.org/issues/1457 Tested by: Fabian Keil Obtained from: Illumos MFC after: 1 month
* | | Unlock IPMI sc while performing requests via KCS and SMIC interfaces.melifaro2013-03-252-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | It is already done in SSIF interface code. This reduces contention/spinning reported by many users. PR: kern/172166 Submitted by: Eric van Gyzen <eric at vangyzen.net> MFC after: 2 weeks
* | | Read Asynchronous Notification statuses only if Port Multiplier or ATAPImav2013-03-251-1/+2
| | | | | | | | | | | | | | | device are connected. ATA disks are not using ANs, while the extra register read operation is quite expensive.
* | | o Typo: IEE -> IEEE.maxim2013-03-251-1/+1
| | | | | | | | | | | | | | | | | | PR: docs/173069 Submitted by: Bjorn Heidotting MFC after: 1 week
* | | Cache the callout precision argument as part of the informations requireddavide2013-03-251-2/+9
| | | | | | | | | | | | | | | | | | | | | | | | for migrating callouts to new CPU. This value is passed to callout_cc_add() in order to update properly precision field in case of rescheduling/migration. Reviewed by: mav
* | | Depending on combination of running commands (NCQ/non-NCQ) try to avoidmav2013-03-251-5/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | extra read from PxCI/PxSACT registers. If only NCQ commands are running, we don't really need PxCI. If only non-NCQ commands are running we don't need PxSACT. Mixed set may happen only on controllers with FIS-based switching when port multiplier is attached, and then we have to read both registers. MFC after: 1 month
* | | When we are removing a specific set, call ipfw_expire_dyn_rules only once.ae2013-03-251-4/+5
| | | | | | | | | | | | | | | Obtained from: Yandex LLC MFC after: 1 week
* | | Make GEOM MULTIPATH to report unmapped bio support if underling path reportmav2013-03-251-0/+2
| | | | | | | | | | | | it. GEOM MULTIPATH itself never touches the data and so transparent.
* | | Remove two bzero()s that are erasing only few more bytes then set later.mav2013-03-251-2/+6
| | |
* | | In GEOM DISK:mav2013-03-251-56/+28
| | | | | | | | | | | | | | | | | | | | | - Replace single done mutex with per-disk ones. On system with several disks on several HBAs that removes small, but measurable lock congestion. - Modify disk destruction process to not destroy the mutex prematurely. - Remove some extra pointer derefences.
* | | Add shlib-compat under tools.gleb2013-03-2531-0/+1833
| | | | | | | | | | | | | | | shlib-compat is ABI compatibility checker for shared libraries with symbol versioning.
* | | sh(1): Mention possible ambiguities with $(( and ((.jilles2013-03-241-1/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | In some other shells, things like $((a);(b)) are command substitutions. Also, there are shells that have an extension ((ARITH)) that evaluates an arithmetic expression and returns status 1 if the result is zero, 0 otherwise. This extension may lead to ambiguity with two subshells starting in sequence.
* | | Note that output is in seconds, not msec.mckusick2013-03-241-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | KNF indentation. No functional change. No change to printf strings. No change to casting of printf arguments. Reported by: Bruce Evans
* | | Dtrace: add optional size argument to tracemem().pfg2013-03-2410-23/+1469
|\ \ \ | |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Merge change from illumos: 1455 DTrace tracemem() should take an optional size argument Our local enhancements to dt_print_bytes were equivalent to those in illumos but we made it match the illumos version to ease further code merges. For now leave out tst.smallsize.d and tst.smallsize.d.out since those don't seem to work cleanly on FreeBSD. This change bumps the DT_VERS_* number to 1.7.1 in accordance to what is done in illumos. Illumos Revision: 13457:571b0355c2e3 Reference: https://www.illumos.org/issues/1455 Tested by: Fabian Keil Obtained from: Illumos MFC after: 1 month
| * | Update vendor/illumos/dist to illumos-gate 13983:fe80600e1f8emm2013-03-143-2/+7
| | | | | | | | | | | | | | | | | | Illumos ZFS issues: 3604 zdb should print bpobjs more verbosely (fix zdb hang) 3606 zpool status -x shouldn't warn about old on-disk format
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-03-122-6/+58
| | | | | | | | | | | | | | | | | | | | | to illumos-gate 13980:d7059eb1884c Illumos ZFS issues: 3598 want to dtrace when errors are generated in zfs
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-03-051-17/+53
| | | | | | | | | | | | | | | | | | | | | | | | to illumos-gate 13977:af7f2603d4d7 Illumos ZFS issues: 3603 panic from bpobj_enqueue_subobj() 3604 zdb should print bpobjs more verbosely
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-03-052-0/+37
| | | | | | | | | | | | | | | | | | | | | | | | to illumos-gate 13975:ef6409bc370f Illumos ZFS issues: 3582 zfs_delay() should support a variable resolution 3584 DTrace sdt probes for ZFS txg states
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-03-0112-288/+520
| | | | | | | | | | | | | | | | | | | | | to illumos-gate 13973:4972ab336f54 Illumos ZFS issues: 3464 zfs synctask code needs restructuring
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-02-261-0/+34
| | | | | | | | | | | | | | | | | | | | | | | | to illumos-gate 13969:b2c7608044b7 Illumos ZFS issues: 3588 provide zfs properties for logical (uncompressed) space used and referenced
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-02-232-7/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | to illumos-gate 13967:92bec6d87f59 Illumos ZFS issues: 3557 dumpvp_size is not updated correctly when a dump zvol's size is changed 3558 setting the volsize on a dump device does not return back ENOSPC 3559 setting a volsize larger than the space available sometimes succeeds
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-02-231-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | to illumos-gate 13959:e03e14ddfb4c Illumos ZFS issues: 3552 condensing one space map burns 3 seconds of CPU in spa_sync() thread 3564 spa_sync() spends 5-10% of its time in metaslab_sync() (when not condensing)
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-02-182-4/+40
| | | | | | | | | | | | | | | | | | | | | to illumos-gate 13957:512faafc0eaf Illumos ZFS issues: 3537 want pool io kstats
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-02-111-1/+5
| | | | | | | | | | | | | | | | | | | | | to illumos-gate 13953:0cc6917308f7 Illumos dtrace issues: 3529 iostat should display time used by dtrace
| * | Update vendor/illumos/dist to illumos-gate version 13944:bbcbb468dc37mm2013-02-0619-34/+158
| | | | | | | | | | | | | | | | | | | | | Illumos dtrace issues: 3519 DTrace fails to resolve const types from fbt 3520 dtrace internal error -- token type 316 is not a valid D compilation token 3521 clean up dtrace unit tests
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-02-061-4/+3
| | | | | | | | | | | | | | | | | | | | | to illumos-gate 13941:d48547176ab4 Illumos ZFS issues: 3498 panic in arc_read(): !refcount_is_zero(&pbuf->b_hdr->b_refcnt)
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-02-061-20/+29
| | | | | | | | | | | | | | | | | | | | | to illumos-gate 13939:20e4d8d8da6d illumos dtrace issues: 3511 dtrace.c erroneously checks for memory alignment on amd64
| * | Update vendor/illumos/dist to illumos-gate version 13936:60077db1e2ccmm2013-02-061-67/+80
| | | | | | | | | | | | | | | Illumos ZFS issues: 3380 zfs man page: documentation for zfs allow is confusing
| * | Update vendor/illumos/dist and vendor-sys/illumos/distmm2013-02-061-7/+1
| | | | | | | | | | | | | | | | | | | | | | | | to illumos-gate 13934:9e23a7f7b812 Illumos ZFS issues: 3422 zpool create/syseventd race yield non-importable pool 3425 first write to a new zvol can fail with EFBIG
OpenPOWER on IntegriCloud