cvs commit: src/sys/sys mdioctl.h src/sys/dev/md md.c
src/sbin/mdconfig mdconfig.8 mdconfig.c
phk at phk.freebsd.dk
Wed Mar 10 22:35:52 PST 2004
In message <188.8.131.52.1.20040311062306.03f9ade0 at imap.sfu.ca>, Colin Percival writ
>At 06:13 11/03/2004, Poul-Henning Kamp wrote:
> >That is a matter of taste more than anything else. A vnode backed md(4)
>>device is technically a layering violation, so either the syncer or
>>the md(4) code itself (or both) needs to be aware of the special case.
> Is it really necessary for vnode-backed memory disks to be
>accessed through the filesystem? Why can't md(4) hijack the
>disk blocks which constitute the file (telling the filesystem
>not to touch them, of course) and translate I/O operations
>directly into I/O on the underlying device?
That would be a really complex solution to a problem which should not
exist in the first place :-)
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
More information about the cvs-src