cvs commit: src/sys/sys mdioctl.h src/sys/dev/md md.c src/sbin/mdconfig mdconfig.8 mdconfig.c

[Colin Percival]

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.

<kernelnewbie>
   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?
</kernelnewbie>

Colin Percival