Date: Fri, 1 Nov 2013 13:23:12 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: symbolics@gmx.com Cc: geom@freebsd.org, hackers@freebsd.org Subject: Re: GEOM mentor request Message-ID: <alpine.BSF.2.00.1311011310340.23437@wonkity.com> In-Reply-To: <20131101103158.GA35397@lemon> References: <20131101103158.GA35397@lemon>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 1 Nov 2013, symbolics@gmx.com wrote: > + Implement new things. Some ideas I have had: > + GEOM "ERASE" - Rewrite deletes into random writes. > + GEOM "PLUG" - Persistent version of the connect/disconnect verbs > where the flag sits in the class metadata. This might be a cleaner > approach, rather than adding the verbs to all the existing > providers. > + GEOM "TAP" - Allow userspace processes to hook into the GEOM > API. Intended for debugging and development. > + GEOM "WCACHE" - Allow you to use small, fast provider as a buffer > for a larger, slower provider. > + GEOM DTrace provider. Provide GEOM specific probes to complement > the IO provider. > + Probably other bits I can't remember right now. How about an explicit geom retaste command? "true > /dev/ada0" is misleading to the reader. Also, a RAM-cached version of gmirror that would report writes finished as soon as the faster drive finishes. Kind of the opposite of the WCACHE above. This would permit creating mirrors of an SSD and hard drive without performance loss, at least up until available write buffer space runs out. This one may not be so easy.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1311011310340.23437>