From: Nuno Silva <nuno.silva@vgertech.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] A quick humfs HOWTO
Date: Thu, 08 Apr 2004 07:25:22 +0100 [thread overview]
Message-ID: <4074F052.20603@vgertech.com> (raw)
In-Reply-To: <200404080207.i3827rbe009294@ccure.user-mode-linux.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jeff Dike wrote:
[..]
|
| The root contains two directories :
| data - which contains the files
| metadata - which shadows "data" and whose files contain ownership
| information
| and one file
| superblock - which contains information about the filesystem as a
| whole
Great news, compiling right now! :-)
In the meanwhile I'm thinking about this system and it seems that this
will eat lots of inodes because every file will be present twice in the
[host] filesystem with the metadata version using only a few bytes. Also
every "ls -la" (if it's not cached) in UML will generate a read in the
file's metafile file (say this 3 times quickly! eheheh). With 1000 files
in a directory thats lot's of fopen()s.
Wouldn't it be better to add support for a simple DB, like sleepycat or
CMU cyrus' project skiplist or even something lighter? This way we can
have only 2 files in the humfs "root", the superblock and the metadataDB.
This can save inodes and improve performance because you have only one
file that's indexed! :-)
The downsides:
- - another linker requirement at build time;
- - can't inspect and/or easily modify permissions with emacs. :-)
Any thoughts?
Regards,
Nuno Silva
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAdPBSOPig54MP17wRAp8zAJ0UWKA5QvAdh4DJSzUfpV+Y5JCywwCgmhz/
S6aXJ9hLzCyJBBNlYSkOVSQ=
=EO+m
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-04-08 6:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 2:07 [uml-devel] A quick humfs HOWTO Jeff Dike
2004-04-08 6:25 ` Nuno Silva [this message]
2004-04-08 8:43 ` Henrik Nordstrom
2004-04-09 18:49 ` BlaisorBlade
2004-04-12 15:06 ` Michael Richardson
2004-04-13 6:51 ` Henrik Nordstrom
2004-04-12 15:05 ` Michael Richardson
2004-04-08 7:58 ` [uml-devel] Re: [uml-user] " Rus Foster
2004-04-08 11:23 ` Jeff Dike
2004-04-08 8:35 ` [uml-devel] " Henrik Nordstrom
2004-04-08 11:34 ` Jeff Dike
2004-04-08 12:09 ` Henrik Nordstrom
2004-04-08 9:54 ` Nick Craig-Wood
2004-04-08 10:07 ` Henrik Nordstrom
2004-04-08 11:41 ` Jeff Dike
2004-04-08 10:26 ` stian
2004-04-08 11:41 ` Jeff Dike
2004-04-08 12:52 ` Jeff Dike
2004-04-08 12:03 ` [uml-devel] " Gerd Knorr
2004-04-08 12:49 ` Jeff Dike
2004-04-08 13:01 ` Gerd Knorr
2004-04-08 13:49 ` Robin Green
2004-04-12 15:11 ` Michael Richardson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4074F052.20603@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.