| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Reviewed by: stass
Obtained From: DragonFlyBSD
MFC After: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Address. Although KAME implementation used FF02:0:0:0:0:2::/96 based on
older versions of draft-ietf-ipngwg-icmp-name-lookup, it has been changed
in RFC 4620.
The kernel always joins the /104-prefixed address, and additionally does
/96-prefixed one only when net.inet6.icmp6.nodeinfo_oldmcprefix=1.
The default value of the sysctl is 1.
ping6(8) -N flag now uses /104-prefixed one. When this flag is specified
twice, it uses /96-prefixed one instead.
Reviewed by: ume
Based on work by: Thomas Scheffler
PR: conf/174957
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
| |
Previously, rc.d/mountlate mounted *all* filesystems, causing problems with
background NFS mounts being mounted twice.
PR: conf/137629
Submitted by: eadler (original concept)
Reviewed by: mjg
Approved by: hrs
|
| |
|
|
|
|
|
|
|
|
| |
names within the std namespace (and possibly within the global
namespace).
The main advantage is that the C++ versions can provide optimized
versions or simplified interfaces.
|
|
|
|
| |
PR: 177188
|
| |
|
|
|
|
|
|
|
| |
in which case unused blocks are first zeroed and then erased.
Reviewed by: mckusick
MFC after: 3 weeks
|
|
|
|
|
| |
I forgot that I still had a locally applied patch to my copy of Clang
that needs to be pushed in before we should use C11 atomics.
|
|
|
|
| |
Reviewed by: pjd
|
|
|
|
|
|
|
|
|
|
|
|
| |
piece them together from multiple reads(). It's as if /dev/devctl is
a datagram device instead of a stream device. However, devd's
internal buffer was too small (1025 bytes) to read an entire
ereport.fs.zfs.checksum event (variable, up to ~1300 bytes). This
commit enlarges the buffer to 8k.
Reviewed by: imp
Approved by: ken (mentor)
MFC after: 2 weeks
|
| |
|
|
|
|
|
| |
PR: bin/178121
Submitted by: Garrett Cooper <yaneurabeya gmail.com>
|
|
|
|
|
|
| |
Reviewed by: mav
Approved by: pjd (mentor)
MFC after: 2 weeks
|
|
|
|
|
| |
Submitted by: Andrey Chernov (ache@)
MFC after: 3 days
|
|
|
|
| |
PR: 177455
|
|
|
|
|
| |
PR: bin/170279
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
than VLAN groups.
Some chips (eg this rtl8366rb) has a VLAN group per port - you first
define a set of VLANs in a vlan group, then you assign a VLAN group
to a port.
Other chips (eg the AR8xxx switch chips) have a VLAN ID array per
port - there's no group per se, just a list of vlans that can be
configured.
So for now, the switch API will use the latter and rely on drivers
doing the heavy lifting if one wishes to use the VLAN group method.
Maybe later on both can be supported.
PR: kern/177878
PR: kern/177873
Submitted by: Luiz Otavio O Souza <loos.br@gmail.com>
Reviewed by: ray
|
|
|
|
|
|
|
| |
Fix this to require an argument.
PR: kern/177872
Submitted by: Luiz Otavio O Souza <loos.br@gmail.com>
|
|
|
|
|
|
|
| |
information.
PR: kern/177871
Submitted by: Luiz Otavio O Souza <loos.br@gmail.com>
|
|
|
|
|
| |
Mark global variables static. While there, make some small style(9)
cleanups and remove a variable that is unused.
|
| |
|
|
|
|
|
| |
PR: 177870
Submitted by: Bjorn Heidotting <b.heidotting@yahoo.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This compiler flag enforces that that people either mark variables
static or use an external declarations for the variable, similar to how
-Wmissing-prototypes works for functions.
Due to the fact that Yacc/Lex generate code that cannot trivially be
changed to not warn because of this (lots of yy* variables), add a
NO_WMISSING_VARIABLE_DECLARATIONS that can be used to turn off this
specific compiler warning.
Announced on: toolchain@
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
replace
them with the NVMe passthrough equivalent.
Sponsored by: Intel
|
| |
|
| |
|
|
|
|
| |
geom(4) manual page SYNOPSIS.
|
|
|
|
|
|
|
| |
We're only interested in the enumeration fields; we don't want to create
a variable to store them.
MFC after: 1 week
|
|
|
|
| |
here.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
disks such as SSD's
Adds the ability to run ATA commands via the SCSI ATA Pass-Through(16) comand
Reviewed by: mav
Approved by: pjd (mentor)
MFC after: 2 weeks
|
|
|
|
| |
Discussed with: mav
|
| |
|
|
|
|
|
|
|
|
|
| |
most kernels before FreeBSD 9.0. Remove such modules and respective kernel
options: atadisk, ataraid, atapicd, atapifd, atapist, atapicam. Remove the
atacontrol utility and some man pages. Remove useless now options ATA_CAM.
No objections: current@, stable@
MFC after: never
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
fail in nvmecontrol(8).
While here, use consistent checks of return values from stat, open and
ioctl.
Sponsored by: Intel
Suggested by: carl
Reviewed by: carl
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
invoke it from nvmecontrol(8).
Controller reset will be performed in cases where I/O are repeatedly
timing out, the controller reports an unrecoverable condition, or
when explicitly requested via IOCTL or an nvme consumer. Since the
controller may be in such a state where it cannot even process queue
deletion requests, we will perform a controller reset without trying
to clean up anything on the controller first.
Sponsored by: Intel
Reviewed by: carl
|
|
|
|
|
|
| |
PR: docs/173069
Submitted by: Bjorn Heidotting
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
KNF indentation.
No functional change.
No change to printf strings.
No change to casting of printf arguments.
Reported by: Bruce Evans
|
|
|
|
|
|
|
| |
compile tested with clang on i386, amd64
compile tested with gcc on i386, amd64, sparc64
Submitted by: delphij
|
|
|
|
|
| |
Submitted by: db
Reviewed by: gjb
|
|
|
|
| |
Build verified by: Glen Barber (gjb@)
|
| |
|
|
|
|
|
| |
Reported by: Glen Barber (gjb@)
Pointy hat to: Kirk McKusick (mckusick@)
|
|
|
|
|
|
|
|
| |
Clang errors around printf could be trivially fixed, but the breakage in
sbin/fsdb were to significant for this type of change.
Submitter of this changeset has been notified and hopefully this can be
restored soon.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that they do not need to be read again in pass5. As this nearly
doubles the memory requirement for fsck, the cache is thrown away
if other memory needs in fsck would otherwise fail. Thus, the
memory footprint of fsck remains unchanged in memory constrained
environments.
This work was inspired by a paper presented at Usenix's FAST '13:
www.usenix.org/conference/fast13/ffsck-fast-file-system-checker
Details of this implementation appears in the April 2013 of ;login:
www.usenix.org/publications/login/april-2013-volume-38-number-2.
A copy of the April 2013 ;login: paper can also be downloaded
from: www.mckusick.com/publications/faster_fsck.pdf.
Reviewed by: kib
Tested by: Peter Holm
MFC after: 4 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
running time for a full fsck. It also reduces the random access time
for large files and speeds the traversal time for directory tree walks.
The key idea is to reserve a small area in each cylinder group
immediately following the inode blocks for the use of metadata,
specifically indirect blocks and directory contents. The new policy
is to preferentially place metadata in the metadata area and
everything else in the blocks that follow the metadata area.
The size of this area can be set when creating a filesystem using
newfs(8) or changed in an existing filesystem using tunefs(8).
Both utilities use the `-k held-for-metadata-blocks' option to
specify the amount of space to be held for metadata blocks in each
cylinder group. By default, newfs(8) sets this area to half of
minfree (typically 4% of the data area).
This work was inspired by a paper presented at Usenix's FAST '13:
www.usenix.org/conference/fast13/ffsck-fast-file-system-checker
Details of this implementation appears in the April 2013 of ;login:
www.usenix.org/publications/login/april-2013-volume-38-number-2.
A copy of the April 2013 ;login: paper can also be downloaded
from: www.mckusick.com/publications/faster_fsck.pdf.
Reviewed by: kib
Tested by: Peter Holm
MFC after: 4 weeks
|