| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This gets rid of the following error message during FreeBSD guest bootup:
"vtbd0: hard error cmd=flush fsbn 0"
Reported by: rodrigc
Reviewed by: grehan
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FreeBSD has ARC_BUFC_NUMMETADATALISTS metadata lists and ARC_BUFC_NUMDATALISTS
data lists (currently both are 16) while illumos has just a single list
of each kind.
headroom determines how much data is scanned on a single list
during each run of the l2arc feed thread.
Because FreeBSD has more lists we proportionally decrease the limit.
Reviewed by: Brendan Gregg (earlier version)
MFC after: 2 weeks
Sponsored by: HybridCluster
|
| |
|
|
|
|
|
|
| |
https://svnweb.freebsd.org/base?view=revision&revision=272347
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
FreeBSD has ARC_BUFC_NUMMETADATALISTS metadata lists and ARC_BUFC_NUMDATALISTS
data lists (currently both are 16) while illumos has just a single list
of each kind.
L2ARC_WRITE_SIZE determines the default value of l2arc_write_max which
defines limits on how much data is scanned and written to a cache device
during each run of the l2arc feed thread. The limits are applied on the
per buffer list basis.
Because FreeBSD has more lists we proportionally reduce the limits.
Reviewed by: Brendan Gregg (earlier version)
MFC after: 2 weeks
Sponsored by: HybridCluster
|
|
|
|
|
|
| |
This should allow zdb -A option to actually make difference.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
Change mbuf's rcvif to enc0 and restore it after pfil processing.
PR: 110959
Sponsored by: Yandex LLC
|
|
|
|
|
| |
MFC after: 3 days
Sponsored by: Mellanox Technologies
|
|
|
|
|
|
|
| |
2) Return error on unsupported format specs.
(both according to POSIX)
PR: 93197
|
|
|
|
|
|
|
| |
POSIX treats negative time_t as undefined (i.e. may be valid too,
depends on system's policy we don't have) and we don't set EOVERFLOW
in mktime/timegm as POSIX requires to surely distinguish -1 return
as valid negative time from -1 as error return.
|
|
|
|
| |
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
Obtained from: OpenBSD
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
| |
one to, for example, access the "provider" field of a struct g_consumer,
even though "provider" is a D keyword.
PR: 169657
MFC after: 2 months
Discussed with: Bryan Cantrill
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
| |
The hypervisor hides the MONITOR/MWAIT capability by unconditionally setting
CPUID.01H:ECX[3] to 0 so the guest should not expect these instructions to
be present anyways.
Discussed with: grehan
|
|
|
|
|
|
|
|
|
|
| |
configuration value is an integer count of seconds, it is not a timeval.
Using memcpy() to copy a timeval from it put garbage into the tv_usec
field.
PR: 194025
Submitted by: David Shane Holden <dpejesh@yahoo.com>
MFC after: 1 week
|
|
|
|
|
| |
PR: 193660
Submitted by: holger@freyther.de
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
run directly on netmap ports using netmap:foo or valeXX:YY device names.
Modifications to existing code are small and trivial, the netmap-specific
code is all in a new file.
Please be aware that in netmap mode the physical interface is disconnected from
the host stack, so libpcap will steal the traffic not just make a copy.
For the full version of the code (including linux and autotools support) see
https://code.google.com/p/netmap-libpcap/
MFC after: 3 days
|
|
|
|
| |
my bug in r271409 that I noticed while reviewing r272492.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
MFC after: 3 days
|
| |
| |
| |
| |
| |
| |
| | |
PR: 194128
Submitted by: Scott M. Ferris <smferris@gmail.com>
MFC after: 3 days
Sponsored by: EMC/Isilon Storage Division
|
| |
| |
| |
| |
| |
| |
| |
| | |
use calloc in get_line() when allocating line to ensure it is fully initialized,
fixes a later uninitialized value in copy_param() (FreeBSD #193499).
PR: 193499
Submitted by: Thomas E. Dickey <tom@invisible-island.net>
|
| |
| |
| |
| | |
MFC after: 3 dayes
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before this change target could send R2T request for write transfer of any
size, that could violate iSCSI RFC, which allows initiator to limit maximum
R2T size by negotiating MaxBurstLength connection parameter.
Also report an error in case of write underflow, when initiator provides
less data than initiator expects. Previously in such case our target
sent R2T request for non-existing data, violating the RFC, and confusing
some initiators. SCSI specs don't explicitly define how write underflows
should be handled and there are different oppinions, but reporting error
is hopefully better then violating iSCSI RFC with unpredictable results.
MFC after: 2 weeks
|
| |
| |
| |
| | |
Obtained from: luigi
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
we can't easily predict (in current parsing model)
if the keyword is ipfw(8) reserved keyword or port name.
Checking proto database via getprotobyname() consumes a lot of
CPU and leads to tens of seconds for parsing large ruleset.
Use list of reserved keywords and check them as pre-requisite
before doing getprotobyname().
Obtained from: Yandex LLC
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It was found that VirtualBox' AHCI does not allow nterrupt to be cleared
before the interrupt status register is read, causing interrupt storm.
AHCI specification allows to skip this register use when multi-vector MSI
is enabled and so interrupting port is known. For single-vector MSI that
is not stated explicitly, but if the port is only one, it is obviously
known too.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Whilst here use tab instead of spaces.
Approved by: stas (mentor)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use loaned ARC buffer for zfs receive to avoid copy.
Illumos issue:
5162 zfs recv should use loaned arc buffer to avoid copy
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| | |
This moves a var to an if statement, no functional changes.
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Handle old format deadlist.
Illumos issue:
5178 zdb -vvvvv on old-format pool fails in dump_deadlist()
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Split the godfather zio into CPU number's to reduce lock
contention.
Illumos issue:
5176 lock contention on godfather zio
MFC after: 2 weeks
|
| |
| |
| |
| | |
MFC after: 3 days
|
| |
| |
| |
| | |
MFC after: 1 week
|
| |
| |
| |
| | |
Suggested by: glebius @
|
| |
| |
| |
| |
| |
| |
| | |
Illumos issue:
5177 remove dead code from dsl_scan.c
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't inherit flags other than DS_FLAG_CI_DATASET and DS_FLAG_INCONSISTENT
when cloning. This prevents DS_FLAG_DEFER_DESTROY being inherited from a
clone that is marked for deferred destroy, which causes snapshots of the
clone being destroyed when getting a hold or clone.
Illumos issue:
5150 zfs clone of a defer_destroy snapshot causes strangeness
MFC after: 1 week
|
| |
| |
| |
| |
| |
| | |
This saves some symbols and function calls for kernel without RACCT.
MFC after: 1 week
|
| | |
|
| |
| |
| |
| | |
Reviewed by: will
|
| |
| |
| |
| |
| | |
Reported by: Oliver Hartmann
X-MFC-With: r272488
|
| | |
|
| |
| |
| |
| |
| |
| | |
Pointy hat to: mjg
Reported by: bz
X-MFC: with r272567
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Acquire the lock in read mode when just needed to ensure the stability
of the keg list. The UMA lock may be held for a long time (relatively
speaking) in uma_reclaim() on machines with lots of zones/kegs. If the
uma_timeout() would fire during that period, subsequent callouts on that
CPU may be significantly delayed.
Reviewed by: jhb
|
| | |
|