Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Jan 2017 18:04:28 +0700
From:      Eugene Grosbein <eugen@grosbein.net>
To:        Julian Elischer <julian@freebsd.org>, Aijaz Baig <aijazbaig1@gmail.com>, "Greg 'groggy' Lehey" <grog@freebsd.org>
Cc:        FreeBSD Hackers <freebsd-hackers@freebsd.org>, freebsd-scsi@freebsd.org
Subject:   Re: Understanding the rationale behind dropping of "block devices"
Message-ID:  <587CA8BC.1070609@grosbein.net>
In-Reply-To: <a86ad6f5-954d-62f0-fdb3-9480a13dc1c3@freebsd.org>
References:  <CAHB2L%2BdRbX=E9NxGLd_eHsEeD0ZVYDYAx2k9h17BR0Lc=xu5HA@mail.gmail.com> <20170116071105.GB4560@eureka.lemis.com> <CAHB2L%2Bd9=rBBo48qR%2BPXgy%2BJDa=VRk5cM%2B9hAKDCPW%2BrqFgZAQ@mail.gmail.com> <a86ad6f5-954d-62f0-fdb3-9480a13dc1c3@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
16.01.2017 16:20, Julian Elischer wrote:

> If you want  device M, at offset N we will fetch it for you from the device, DMA'd directly into your address space,
> but there is no cached copy.
> Having said that, it would be trivial to add a 'caching' geom layer to the system but that has never been needed.

In fact, FreeBSD does have geom_cache/gcache(8) for long time. It is block-level read cache
passing write requests through transparently.

It is unmaintained, though and there were some reports that it is suspected to cause kernel panics
if there are more than one active GEOM_CACHE instances in a system.

> The added complexity of carrying around two alternate interfaces to the same devices was judged by those who did the work to be not worth the small gain available to the very few people who used raw devices.
> Interestingly, since that time ZFS has implemented a block-layer cache for itself which is of course not integrated with the non-existing block level cache in the system :-).




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?587CA8BC.1070609>