committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
abdef0123 filter by commit's SHA hash.
rNNN filter by SVN revision.
rNNN-rMMM filter by SVN revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|a6840191||adrian||July 26, 2016, 4:40 p.m.||Update my TODO items.|
|8ee0bdb9||emaste||July 26, 2016, 3:34 p.m.||vt: lock Giant around kbd calls in CONS_GETINFO|
|bbecb73b||emaste||July 26, 2016, 1:36 p.m.||apply some style(9) to kbd: make function name start in column 1|
|34c30e12||sephe||July 26, 2016, 5:06 a.m.||hyperv/vmbus: Nuke unnecessary accessor functions.|
|e7f94194||bdrewery||July 26, 2016, 3:47 a.m.||Add links for bit_ffc_at(3) and bit_ffs_at(3).|
|6a5bc1d1||sbruno||July 26, 2016, 12:02 a.m.||iwm(4) synchronize driver to DragonFlyBSD version and recent f/w update.|
|33c7715f||sbruno||July 25, 2016, 11:44 p.m.||iwm(4): switch to ieee80211_runtask()|
|e4ff4297||sbruno||July 25, 2016, 11:05 p.m.||Update iwmfw(4) to include support for 8260 series units and update|
|25458cbe||behlendorf1||July 25, 2016, 10:26 p.m.||Limit the amount of dnode metadata in the ARC
Metadata-intensive workloads can cause the ARC to become permanently filled with dnode_t objects as they're pinned by the VFS layer. Subsequent data-intensive workloads may only benefit from about 25% of the potential ARC (arc_c_max - arc_meta_limit). In order to help track metadata usage more precisely, the other_size metadata arcstat has replaced with dbuf_size, dnode_size and bonus_size. The new zfs_arc_dnode_limit tunable, which defaults to 10% of zfs_arc_meta_limit, defines the minimum number of bytes which is desirable to be consumed by dnodes. Attempts to evict non-metadata will trigger async prune tasks if the space used by dnodes exceeds this limit. The new zfs_arc_dnode_reduce_percent tunable specifies the amount by which the excess dnode space is attempted to be pruned as a percentage of the amount by which zfs_arc_dnode_limit is being exceeded. By default, it tries to unpin 10% of the dnodes. The problem of dnode metadata pinning was observed with the following testing procedure (in this example, zfs_arc_max is set to 4GiB): - Create a large number of small files until arc_meta_used exceeds arc_meta_limit (3GiB with default tuning) and arc_prune starts increasing. - Create a 3GiB file with dd. Observe arc_mata_used. It will still be around 3GiB. - Repeatedly read the 3GiB file and observe arc_meta_limit as before. It will continue to stay around 3GiB. With this modification, space for the 3GiB file is gradually made available as subsequent demands on the ARC are made. The previous behavior can be restored by setting zfs_arc_dnode_limit to the same value as the zfs_arc_meta_limit. Signed-off-by: Tim Chase <firstname.lastname@example.org> Signed-off-by: Brian Behlendorf <email@example.com> Issue #4345 Issue #4512 Issue #4773 Closes #4858cgit
|e6603b7c||behlendorf1||July 25, 2016, 9:24 p.m.||Fix sync behavior for disk vdevs
Prior to b39c22b, which was first generally available in the 0.6.5 release as b39c22b, ZoL never actually submitted synchronous read or write requests to the Linux block layer. This means the vdev_disk_dio_is_sync() function had always returned false and, therefore, the completion in dio_request_t.dr_comp was never actually used. In b39c22b, synchronous ZIO operations were translated to synchronous BIO requests in vdev_disk_io_start(). The follow-on commits 5592404 and aa159af fixed several problems introduced by b39c22b. In particular, 5592404 introduced the new flag parameter "wait" to __vdev_disk_physio() but under ZoL, since vdev_disk_physio() is never actually used, the wait flag was always zero so the new code had no effect other than to cause a bug in the use of the dio_request_t.dr_comp which was fixed by aa159af. The original rationale for introducing synchronous operations in b39c22b was to hurry certains requests through the BIO layer which would have otherwise been subject to its unplug timer which would increase the latency. This behavior of the unplug timer, however, went away during the transition of the plug/unplug system between kernels 2.6.32 and 2.6.39. To handle the unplug timer behavior on 2.6.32-2.6.35 kernels the BIO_RW_UNPLUG flag is used as a hint to suppress the plugging behavior. For kernels 2.6.36-2.6.38, the REQ_UNPLUG macro will be available and ise used for the same purpose. Signed-off-by: Tim Chase <firstname.lastname@example.org> Signed-off-by: Brian Behlendorf <email@example.com> Closes #4858cgit
|273ff9b5||behlendorf1||July 25, 2016, 9:21 p.m.||Fix uninitialized variable in avl_add()
Silence the following warning when compiling with gcc 5.4.0. Specifically gcc (Ubuntu 5.4.0-6ubuntu1~16.04.1) 5.4.0 20160609. module/avl/avl.c: In function ‘avl_add’: module/avl/avl.c:647:2: warning: ‘where’ may be used uninitialized in this function [-Wmaybe-uninitialized] avl_insert(tree, new_node, where); Signed-off-by: Brian Behlendorf <firstname.lastname@example.org>cgit
|d5887f37||rene||July 25, 2016, 8:49 p.m.||miwi resigned from FreeBSD, update the graph|
|2c6abf15||behlendorf1||July 25, 2016, 8:21 p.m.||Remove znode's z_uid/z_gid member
Remove duplicate z_uid/z_gid member which are also held in the generic vfs inode struct. This is done by first removing the members from struct znode and then using the KUID_TO_SUID/KGID_TO_SGID macros to access the respective member from struct inode. In cases where the uid/gids are being marshalled from/to disk, use the newly introduced zfs_(uid|gid)_(read|write) functions to properly save the uids rather than the internal kernel representation. Signed-off-by: Nikolay Borisov <email@example.com> Signed-off-by: Brian Behlendorf <firstname.lastname@example.org> Issue #4685 Issue #227cgit
|82a1b2d6||behlendorf1||July 25, 2016, 8:21 p.m.||Check whether the kernel supports i_uid/gid_read/write helpers
Since the concept of a kuid and the need to translate from it to ordinary integer type was added in kernel version 3.5 implement necessary plumbing to be able to detect this condition during compile time. If the kernel doesn't support the kuid then just fall back to directly accessing the respective struct inode's members Signed-off-by: Nikolay Borisov <email@example.com> Signed-off-by: Brian Behlendorf <firstname.lastname@example.org> Issue #4685 Issue #227cgit
|77943bc1||behlendorf1||July 25, 2016, 8:21 p.m.||Fix for metaslab_fastwrite_unmark() assert failure
Currently there is an issue where metaslab_fastwrite_unmark() unmarks fastwrites on vdev_t's that have never had fastwrites marked on them. The 'fastwrite mark' is essentially a count of outstanding bytes that will be written to a vdev and is used in syncing context. The problem stems from the fact that the vdev_pending_fastwrite field is not being transferred over when replacing a top-level vdev. As a result, the metaslab is marked for fastwrite on the old vdev and unmarked on the new one, which brings the fastwrite count below zero. This fix simply assigns vdev_pending_fastwrite from the old vdev to the new one so this count is not lost. Signed-off-by: Tom Caputi <email@example.com> Signed-off-by: Brian Behlendorf <firstname.lastname@example.org> Closes #4267cgit