From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <a019408d7aba0fd73990e4de1b13e20c@proxima.alt.za>
To: 9fans@9fans.net
Date: Sat,  7 Mar 2009 07:00:26 +0200
From: lucio@proxima.alt.za
In-Reply-To: <20090307030128.GA64231@mero.morphisms.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] threads vs forks
Topicbox-Message-UUID: b5479612-ead4-11e9-9d60-3106f5b1d025

> Where does all this fancy stuff belong?  In the storage medium,
> in the HBA, in the device driver, in the file system, or in the
> application?

In a very intelligent cache?  Or did you mention that above and in my
ignorance I missed it?

OK, let's try this:

. Storage medium: only the hardware developers have access to that and
  they have never seemed interested in matching anyone else's
  requirements or suggestions.

. The HBA (?).  If that's the device adapter, the same applies as
  above.

. The device driver should not be very complex and the block handling
  should hopefully be shared by more than one device driver, which
  with the effective demise of Streams is not a very easy thing to
  implement without resorting to jumping through flaming hoops.

. The application?  That's being facetious, surely?

. A cache?  As quanstro pointed out, flash makes a wonderful WORM.
  Now to get Fossil to work as originally intended, or a more suitable
  design and implementation to take its place in this role and we have
  a winner.

++L