From: Latchesar Ionkov <lucho@gmx.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fuse bashing
Date: Tue, 24 Jan 2006 19:26:08 -0500 [thread overview]
Message-ID: <20060125002608.GB8690@ionkov.net> (raw)
In-Reply-To: <a4e6962a0601241337t55fb8031w37822d37b78b18df@mail.gmail.com>
Is there ramfs for FUSE?
Thanks,
Lucho
On Tue, Jan 24, 2006 at 03:37:54PM -0600, Eric Van Hensbergen said:
> On 1/24/06, quanstro@quanstro.net <quanstro@quanstro.net> wrote:
> > On Mon Jan 23 20:21:36 CST 2006, lucho@gmx.net wrote:
> > > On Mon, Jan 23, 2006 at 12:06:09PM -0500, Russ Cox said:
> > > > It appears to match the kernel better, so the implementation
> > > > should be simpler. (As soon as you want to talk between
> > >
> > > It is much simpler (and probably faster), and that's a big win for FUSE:
> > >
> > > $ cat fs/fuse/*.[ch] | wc -l
> > > 4073
> > >
> > > $ cat 9p/*.[ch] | wc -l
> > > 7271
> >
>
> There's likely quite a bit more complexity in the 9P kernel modules.
> As was pointed out earlier, FUSE basically just gateways VFS calls to
> user-space. This is an oversimplificaiton, but its not doing any of
> the mapping we are doing in v9fs.
>
> I'm not willing to say FUSE sucks, it is what it is, and for some
> folks its going to be the right solution. However, for the file
> systems I wanted to write, it wasn't a good match and for file systems
> of any complexity the FUSE user-space code seems to get out of hand
> quickly.
>
> Which brings up a good point for folks who are wc -l 'ing -- anyone
> look at the relative sizes of ramfs coded in 9P and FUSE (including
> their library code)?
>
> -eric
next prev parent reply other threads:[~2006-01-25 0:26 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 20:10 quanstro
2006-01-24 21:37 ` Eric Van Hensbergen
2006-01-24 23:14 ` Charles Forsyth
2006-01-25 0:26 ` Latchesar Ionkov [this message]
2006-01-25 0:25 ` Latchesar Ionkov
2006-01-25 1:31 ` erik quanstrom
2006-01-25 1:40 ` Latchesar Ionkov
2006-01-25 1:42 ` Eric Van Hensbergen
[not found] <000001c620ca$f86f1570$14aaa8c0@utelsystems.local>
2006-01-24 9:46 ` "Nils O. Selåsdal"
-- strict thread matches above, loose matches on Subject: below --
2006-01-23 17:06 Russ Cox
2006-01-23 17:28 ` Ronald G Minnich
2006-01-23 17:44 ` David Leimbach
2006-01-23 18:07 ` Eric Van Hensbergen
2006-01-23 18:13 ` Bruce Ellis
2006-01-23 20:31 ` David Leimbach
2006-01-23 20:33 ` Ronald G Minnich
2006-01-23 23:28 ` Dan Cross
2006-01-23 23:53 ` David Leimbach
2006-01-24 0:07 ` Ronald G Minnich
2006-01-25 19:58 ` Enache Adrian
2006-01-25 20:30 ` Christoph Lohmann
2006-01-25 20:51 ` Ronald G Minnich
2006-01-25 21:09 ` Bruce Ellis
2006-01-25 20:50 ` Ronald G Minnich
2006-01-25 21:09 ` Enache Adrian
2006-01-24 0:12 ` John Barham
2006-01-25 5:29 ` Dave Eckhardt
2006-01-25 15:38 ` Ronald G Minnich
2006-01-25 21:31 ` Dave Eckhardt
2006-01-26 1:16 ` erik quanstrom
2006-01-25 5:30 ` Dave Eckhardt
2006-01-25 7:46 ` Jack Johnson
2006-01-25 8:11 ` Lyndon Nerenberg
2006-01-25 8:18 ` Lyndon Nerenberg
2006-01-25 9:46 ` Andriy G. Tereshchenko
2006-01-25 15:45 ` Ronald G Minnich
2006-01-23 17:51 ` C H Forsyth
2006-01-23 17:46 ` David Leimbach
2006-01-23 20:08 ` Ronald G Minnich
2006-01-23 18:46 ` Skip Tavakkolian
2006-01-24 2:22 ` Latchesar Ionkov
2006-01-24 8:37 ` Charles Forsyth
2006-01-24 9:41 ` Charles Forsyth
2006-01-24 10:04 ` Charles Forsyth
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=20060125002608.GB8690@ionkov.net \
--to=lucho@gmx.net \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).