From: Bernard Hatt <bernard.hatt@ntlworld.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Yet another filesystem - sffs
Date: Tue, 30 Nov 2004 19:45:58 +0000 [thread overview]
Message-ID: <41ACCDF6.5060307@ntlworld.com> (raw)
In-Reply-To: <cohlov$s7p$1@news.cistron.nl>
Miquel van Smoorenburg wrote:
> I've been using such a filesystem for years, since Linux 2.0 ..
> It's at ftp://ftp.cistron.nl/pub/people/miquels/kernel/v2.[0246]/rawfs-*
> Mike.
Yes, it depends how much functionality you *need*, sffs implements
more file operations so that you can do things like:
mkisofs -o /mnt/test/blah.iso [...]
and cdrecord -v -data /mnt/test/blah.iso (without needing isosize).
But what is odd, having run my benchmarks on rawfs, that sffs
is faster by between (0.5% and 4.6%) where I was expecting
almost identical results (but then, benchmarks aren't everything).
Regards,
Bernard
next prev parent reply other threads:[~2004-11-30 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 8:22 Yet another filesystem - sffs Bernard Hatt
2004-11-30 11:32 ` Miquel van Smoorenburg
2004-11-30 19:45 ` Bernard Hatt [this message]
2004-11-30 13:23 ` Pavel Machek
2004-11-30 15:24 ` Martin Mares
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=41ACCDF6.5060307@ntlworld.com \
--to=bernard.hatt@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miquels@cistron.nl \
/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