Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Feb 2019 09:48:59 +0000
From:      Stilez <stilezy@gmail.com>
To:        <freebsd-fs@freebsd.org>
Subject:   Correct upstream tracker for zfs feature request?
Message-ID:  <168e11c0ef8.2766.49a377fccbf53440a4b582c142a1ed88@gmail.com>
In-Reply-To: <168e110a900.2766.49a377fccbf53440a4b582c142a1ed88@gmail.com>
References:  <168e110a900.2766.49a377fccbf53440a4b582c142a1ed88@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
I'd like to submit a feature request for a small handful of zfs sysctls to
be added. But it's pretty opaque where the best upstream tracker would be,
or if they're all synced and equivalent.

It's probably relevant to all zfs ports deriving from illumos/openzfs. The
request would add control over zfs dedup block size (similar to those over
spacemap block size), which is unhelpfully hard-coded, and exposure of
monolithic ARC metadata usage/evictions into rather more insightful/helpful
components of spacemap/dedup/other.

URL for info: https://www.illumos.org/issues/10295

I originally posted the request on the illumos tracker; they suggested the
FreeBSD tracker, but before doing so, id like to check whether in fact to
crosspost/repost on the FreeBSD tracker, or an OpenZFS tracker.

Thanks
Stilez






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?168e11c0ef8.2766.49a377fccbf53440a4b582c142a1ed88>