On Tue, Nov 06, 2001 at 10:26:59AM +0100, Marcus Brinkmann wrote:
> Data blocks don't go to storeio. The included libstore communicates with
> storeio about the storage type and does the actual reading/writing etc
> itself (see file_get_storage_info, store_create, store_encode and
> store_decode). ext2fs is linked to libstore, of course.
I see that storeio have a option "-e" that hide the device. I suppose that
using this option cause ext2fs to go through the storeio translator. So in
this case I can happily implement caching in storeio (even if we use more CPU).
I think that storeio is the only possibility to put a cache mechanism in
user space. But I see some drawbacks:
- memory user for caching can be paged out
- some extra cpu cycle are needed to do I/O
I have already a small library implementing a fixed size cache, so I can
integrate it in the storeio.
Any suggestion?
TIA
--
Saluti / Regards
Diego Roversi | diegor at maganet.net
| diegor at tiscalinet.it
_______________________________________________
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
