| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: jkoshy, gj, dfr
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
bits were granted. Relationships have been provided by the mentees,
dates have been sourced from either the mentees or the CVS mailing list
archives.
Obtained from: mux, wilko, msmith, peter, schweikh
Obtained from: gallatin, dfr, murray, jkoshy
|
|
|
|
| |
MFC after: 1 month
|
| |
|
|
|
|
|
|
|
| |
- Add phk -> mux relationship, confirmed by mux@
- Add scottl -> sbruno relationship
- Move four ex-committers to the alumni section
- Sort.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
on this controller. Indicate that the 5300 is the *only* controller that
will only work in simple mode.
Bus rescans should not be needed now and I consider it a bug if disks do
not appear or dissapear when created or destroyed.
Obtained from: Yahoo! Inc
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Introduce counter(9) API, that implements fast and raceless counters,
provided (but not limited to) for gathering of statistical data.
See http://lists.freebsd.org/pipermail/freebsd-arch/2013-April/014204.html
for more details.
In collaboration with: kib
Reviewed by: luigi
Tested by: ae, ray
Sponsored by: Nginx, Inc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These zones have slab size == sizeof(struct pcpu), but request from VM
enough pages to fit (uk_slabsize * mp_ncpus). An item allocated from such
zone would have a separate twin for each CPU in the system, and these twins
are at a distance of sizeof(struct pcpu) from each other. This magic value
of distance would allow us to make some optimizations later.
To address private item from a CPU simple arithmetics should be used:
item = (type *)((char *)base + sizeof(struct pcpu) * curcpu)
These arithmetics are available as zpcpu_get() macro in pcpu.h.
To introduce non-page size slabs a new field had been added to uma_keg
uk_slabsize. This shifted some frequently used fields of uma_keg to the
fourth cache line on amd64. To mitigate this pessimization, uma_keg fields
were a bit rearranged and least frequently used uk_name and uk_link moved
down to the fourth cache line. All other fields, that are dereferenced
frequently fit into first three cache lines.
Sponsored by: Nginx, Inc.
|
| |
|
|
|
|
|
|
|
| |
Also add cross reference to the icmp6(4).
PR: 177696
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
Approved by: eadler (mentor)
|
|
|
|
|
|
| |
While in the repository, add myself to calendar.freebsd.
Approved by: jpaetzel (mentor)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
hw.igb.num_queues for those so inclined.
PR: kern/177384
Submitted by: hiren.panchasara@gmail.com
Reviewed by: sbruno@
Approved by: jfv@
Obtained from: Yahoo! Inc.
MFC after: 2 weeks
|
|
|
|
|
| |
PR: 177593
Reviewed by: obrien
|
|
|
|
|
|
|
|
| |
This change is not intended for MFC.
PR: docs/177570
Submitted by: Garrett Cooper <yaneurabeya@gmail.com> (partial)
Approved by: bcr (mentor)
|
| |
|
|
|
|
|
| |
Reviewed by: ken
Sponsored by: FreeBSD Foundation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change the default compiler for little-endian ARM to clang to allow for more
testing before 10.0 is released. As LLVM and clang currnetly lack support
for big-endian ARM leave gcc as the default there.
This will also allow us to investigate moving to use the hard floating-point
version of the ARM EABI on SoCs that include the Vector Floating Point unit.
A version of this is included in all ARMv6 and ARMv7 SoCs we currently, and
are likely to support.
Both the current ABI and the new EABI are supported by clang and it will be
built correctly depending on which is selected by the user.
|
|
|
|
|
|
|
|
| |
debugging of the guest via kgdb.
See also: https://wiki.freebsd.org/BHyVe/gdb
Obtained from: NetApp
|
|
|
|
| |
Approved by: crees (mentor)
|
|
|
|
|
|
|
| |
deleted by a "make clean" when DEBUG_FLAGS is set.
Reported by: gleb
Approved by: emaste (co-mentor)
|
|
|
|
|
|
| |
This avoids having separate cases in the install rule for PROGNAME set and
not set. This is a minor cleanup in advance of further support for
standalone debug files.
|
|
|
|
|
| |
This avoids silently failing to include ${SRCCONF} specified by a make(1)
invocation.
|
|
|
|
|
|
|
|
| |
already defined. Setting it with "+=" makes it possible for other make
scripts (e.g. bsd.dtrace.mk) to include additional object files in the
linker arguments.
Approved by: emaste (co-mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The scope of these callbacks is primarily to support actions that affect the
taskqueue's thread environments. They are entirely optional, and
consequently are introduced as a new API: taskqueue_set_callback().
This interface allows the caller to specify that a taskqueue requires a
callback and optional context pointer for a given callback type.
The callback types included in this commit can be used to register a
constructor and destructor for thread-local storage using osd(9). This
allows a particular taskqueue to define that its threads require a specific
type of TLS, without the need for a specially-orchestrated task-based
mechanism for startup and shutdown in order to accomplish it.
Two callback types are supported at this point:
- TASKQUEUE_CALLBACK_TYPE_INIT, called by every thread when it starts, prior
to processing any tasks.
- TASKQUEUE_CALLBACK_TYPE_SHUTDOWN, called by every thread when it exits,
after it has processed its last task but before the taskqueue is
reclaimed.
While I'm here:
- Add two new macros, TQ_ASSERT_LOCKED and TQ_ASSERT_UNLOCKED, and use them
in appropriate locations.
- Fix taskqueue.9 to mention taskqueue_start_threads(), which is a required
interface for all consumers of taskqueue(9).
Reviewed by: kib (all), eadler (taskqueue.9), brd (taskqueue.9)
Approved by: ken (mentor)
Sponsored by: Spectra Logic
MFC after: 1 month
|
| |
|
|
|
|
|
| |
only those that at least are used in the kernel, or that definitely
work.
|
| |
|
|
|
|
| |
Submitted by: Dmitry Luhtionov <dmitryluhtionov gmail.com>
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
includes MFV 238590, 238592, 247580
MFV 238590, 238592:
In the first zfs ioctl restructuring phase, the libzfs_core library was
introduced. It is a new thin library that wraps around kernel ioctl's.
The idea is to provide a forward-compatible way of dealing with new
features. Arguments are passed in nvlists and not random zfs_cmd fields,
new-style ioctls are logged to pool history using a new method of
history logging.
http://blog.delphix.com/matt/2012/01/17/the-future-of-libzfs/
MFV 247580 [1]:
To address issues of several deadlocks and race conditions the locking
code around dsl_dataset was rewritten and the interface to synctasks
was changed.
User-Visible Changes:
"zfs snapshot" can create more arbitrary snapshots at once (atomically)
"zfs destroy" destroys multiple snapshots at once
"zfs recv" has improved performance
Backward Compatibility:
I have extended the compatibility layer to support full backward
compatibility by remapping or rewriting the responsible ioctl arguments.
Old utilities are fully supported by the new kernel module.
Forward Compatibility:
New utilities work with old kernels with the following restrictions:
- creating, destroying, holding and releasing of multiple snapshots
at once is not supported, this includes recursive (-r) commands
Illumos ZFS issues:
2882 implement libzfs_core
2900 "zfs snapshot" should be able to create multiple,
arbitrary snapshots at once
3464 zfs synctask code needs restructuring
References:
https://www.illumos.org/issues/2882
https://www.illumos.org/issues/2900
https://www.illumos.org/issues/3464 [1]
MFC after: 1 month
Sponsored by: Hybrid Logic Inc. [1]
|
| |\ |
|
| |\ \ |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
not yet working, ioctl handling needs to be changed
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This change allows creating file descriptors with close-on-exec set in some
situations. SOCK_CLOEXEC and SOCK_NONBLOCK can be OR'ed in socket() and
socketpair()'s type parameter, and MSG_CMSG_CLOEXEC to recvmsg() makes file
descriptors (SCM_RIGHTS) atomically close-on-exec.
The numerical values for SOCK_CLOEXEC and SOCK_NONBLOCK are as in NetBSD.
MSG_CMSG_CLOEXEC is the first free bit for MSG_*.
The SOCK_* flags are not passed to MAC because this may cause incorrect
failures and can be done later via fcntl() anyway. On the other hand, audit
is expected to cope with the new flags.
For MSG_CMSG_CLOEXEC, unp_externalize() is extended to take a flags
argument.
Reviewed by: kib
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | | |
PR: misc/177106
Submitted by: Hiren Panchasara <hiren.panchasara gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Requested by: alfred, julian
Obtained from: NetApp
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
PR: kern/147237 (based on the initial patch for 8.x)
Tested by: glebius (device detection and suspend/resume)
MFC after: 1 month
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
manager is absent in FreeBSD since 6.0-RELEASE.
Reviewed by: joel
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|