| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
prior to 3.0.0 release). This version is likely very close to what will be
3.0.0.
|
|
|
|
|
| |
Poked by: gjb
MFC after: 3 weeks
|
|
|
|
| |
MFC after: 3 weeks
|
|
|
|
|
| |
Obtained from: OpenBSD
MFC after: 3 weeks
|
|
|
|
|
|
| |
ports. This currently is a nop, but will soon be used to allow
support for multiple boards to be built into one kernel (starting with
AT91RM9200 and expanding out from there).
|
|
|
|
|
|
|
| |
Thanks to ray@, Sevan and Sergey Dyatko for feedback and testing!
Obtained from: OpenBSD
MFC after: 3 weeks
|
| |
|
|
|
|
| |
Revert part of r234723 by re-enabling the SMP protection for intr_bind().
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two aspects to the sequential access optimization: (1) read ahead
of pages that are expected to be accessed in the near future and (2) unmap
and cache behind of pages that are not expected to be accessed again. This
revision changes both aspects.
The read ahead optimization is now more effective. It starts with the same
initial read window as before, but arithmetically grows the window on
sequential page faults. This can yield increased read bandwidth. For
example, on one of my machines, a program using mmap() to read a file that
is several times larger than the machine's physical memory takes about 17%
less time to complete.
The unmap and cache behind optimization is now more selectively applied.
The read ahead window must grow to its maximum size before unmap and cache
behind is performed. This significantly reduces the number of times that
pages are unmapped and cached only to be reactivated a short time later.
The unmap and cache behind optimization now clears each page's referenced
flag. Previously, in the case of dirty pages, if the containing file was
still mapped at the time that the page daemon examined the dirty pages,
they would be reactivated.
From a stylistic standpoint, this revision also cleanly separates the
implementation of the read ahead and unmap/cache behind optimizations.
Glanced at: kib
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
| |
newbie-friendly.
Requested by: jhb, gcooper
Approved by: cperciva (implicit)
MFC after: 3 days
X-MFC-With: r235209
|
|
|
|
|
|
| |
ataraid(4) previously was present there and having GEOM RAID is convinient.
Unlike other classes GEOM RAID can be set up from BIOS before install and
users are expecting it to be detected automatically.
|
|
|
|
|
| |
6.0 support and bump the minimum version to 8.0. These versions have
not been tested and are believed to be broken.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2703 add mechanism to report ZFS send progress
If the zfs send command is used with the -v flag, the amount of bytes
transmitted is reported in per second updates.
References:
https://www.illumos.org/issues/2703
Obtained from: illumos (issue #2703)
MFC after: 2 weeks
|
|
|
|
|
| |
Reviewed by: jhb
MFC after: 1 month
|
|
|
|
| |
redundant SC_LOOKUP() calling.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Partial import of illumos changeset 13622:e5889df1eaac
2077 lots of unreachable breaks in illumos gate
References:
https://www.illumos.org/issues/2077
PR: kern/167370
Submitted by: Marcelo Araujo <araujo@FreeBSD.org>
Obtained from: illumos (issue #2077)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
with the -f flag.
Reimplementation of the illumos changeset 13677:a0cbef703c12
2635 'zfs rename -f' to perform force unmount
References:
https://www.illumos.org/issues/2635
PR: kern/164447
Suggested by: Marcelo Araujo <araujo@FreeBSD.org>
Obtained from: illumos (issue #2635)
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2088 zdb could use a reasonable manual page
Rewrite new zdb manpage to mdoc(7)
References:
https://www.illumos.org/issues/2088
PR: kern/167467 [1]
Submitted by: Marcelo Araujo <araujo@FreeBSD.org> [1]
Reviewed by: mm
Obtained from: Illumos (issue #2088)
MFC after: 1 week
|
|
|
|
|
|
| |
PR: 167696
Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
as possible when using more than one igb(4) adapter. This
means that queues will not be bound to the same CPUs if
there are more CPUs availble.
This is only applicable to a system that has multiple interfaces.
Obtained from: Yahoo! Inc.
MFC after: 3 days
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
for update.
PR: bin/152856
Approved by: cperciva
MFC after: 3 days
|
|
|
|
|
|
| |
the Makefile with boot1.
Submitted by: ru
|
|
|
|
|
|
|
| |
but these don't exist, the code panics.
I should really just add or use a DFS HAL capability before doing this,
so the methods wouldn't be needed..
|
|
|
|
|
|
|
| |
PR: bin/167463
Submitted by: "Bryan Drewery" <bryan@shatow.net>
Approved by: cperciva
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
PR: conf/166460
Submitted by: Jeremy Chadwick <freebsd@jdc.parodius.com>
Reviewed by: stable@
Approved by: cperciva
MFC after: 2 weeks
|
|
|
|
|
| |
Approved by: cperciva
MFC after: 3 days
|
|
|
|
|
| |
Approved by: cperciva
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
when it finds corrupt data.
PR: kern/165695
Submitted by: Robert Simmons <rsimmons0@gmail.com>
Reviewed by: pjd
Approved by: cperciva
MFC after: 1 week
|
|
|
|
| |
Reported by: trasz
|
| |
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
| |
... to avoid name clash with the other libzfs
MFC after: 1 month
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Place the arguments at a fixed offset of 0x800 withing the argument area
(of size 0x1000). Allow variable size extended arguments first of which
should be a size of the extended arguments (including the size
parameter).
Consolidate all related definitions in a new i386/common/bootargs.h header.
Many thanks to jhb and bde for their guidance and reviews.
Reviewed by: jhb, bde
Approved by: jhb
MFC after: 1 month
|
| |
|
|
|
|
|
| |
not being defined. Otherwise we don't make a new make when the old
make is incompatible.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
controller to perform MDIO type accesses to a remote transceiver
using message pages defined through MRBE(multirate backplane
ethernet). It's used in blade systems(e.g Dell Blade m610) which
are connected to pass-through blades rather than traditional
switches.
This change directly manipulates firmware's mailboxes to control
remote PHY such that it does not use mii(4). Alternatively, as
David said, it could be implemented in brgphy(4) by creating a fake
PHY and let brgphy(4) do necessary mii accesses and bce(4) can
implement mailbox accesses based on the type of brgphy(4)'s mii
accesses. Personally, I think it would make brgphy(4) hard to
maintain since it would have to access many bce(4) registers in
brgphy(4). Given that there are users who are suffering from lack
of remote PHY support, it would be better to get working system
rather than waiting for complete/perfect implementation.
Tested by: Jan Winter ( jan.winter <> kantarmedia dot de )
Reviewed by: davidch (initial version)
MFC after: 2 weeks
|
|
|
|
| |
next KDTRACE_HOOKS.
|
|
|
|
|
| |
bootp+nfs code from working as it calls init on each dhcp send and rx fails to
start in time.
|
|
|
|
|
| |
Submitted by: davidch
MFC after: 1 day
|
|
|
|
|
| |
first or this will panic. Condense three blocks that check sc->tsec_ifp into
one while I am here.
|
|
|
|
|
| |
Submitted by: Greg Bednarek <gbednarek averesystems com>
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
64 bits platforms. Let rtld(1) decide if it needs to honor it
or not.
While here, fix a small bug in error reporting when asprintf(3)
returns an error.
Submitted by: kib
Reviewed by: kib (mentor)
MFC after: 1 week
|
|
|
|
|
| |
PR: 167713
Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org)
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
buffer directly.
Approved by: rmacklem (mentor)
MFC after: 1 month
|
|
|
|
|
|
|
|
|
| |
TX and RX PCU stop/drain routines have been thoroughly debugged.
It's also very likely that I should add hooks back up to the
interface glue (if_ath_pci / if_ath_ahb) to do any relevant
bus flushes that are required. A WMAC DDR flush may be required
for the AR9130 SoC.
|