From: Matthew Wilcox <matthew@wil.cx>
To: Al Boldi <a1426z@gawab.com>
Cc: Theodore Tso <tytso@mit.edu>, linux-fsdevel@vger.kernel.org
Subject: Re: Allocation strategy - dynamic zone for small files
Date: Tue, 14 Nov 2006 08:46:30 -0700 [thread overview]
Message-ID: <20061114154630.GB19143@parisc-linux.org> (raw)
In-Reply-To: <200611141843.39745.a1426z@gawab.com>
On Tue, Nov 14, 2006 at 06:43:39PM +0300, Al Boldi wrote:
> An API would probably be in order.
>
> Performance due to non-redundancy.
>
> Or a desire to let people choose what they want.
>
> Think freedom...
How about fewer "visionary statements" and more code? Or at least an
architecture description. Or a rough prototype that shows how we can
make some improvements. You're looking remarkably content-free right now.
next prev parent reply other threads:[~2006-11-14 15:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 10:37 Allocation strategy - dynamic zone for small files Ihar `Philips` Filipau
2006-11-13 13:56 ` avishay
2006-11-13 17:46 ` Bryan Henderson
2006-11-13 19:38 ` Josef Sipek
2006-11-13 21:12 ` Bryan Henderson
2006-11-13 23:32 ` Ihar `Philips` Filipau
2006-11-13 23:57 ` Andreas Dilger
2006-11-14 2:19 ` Dave Kleikamp
2006-11-14 13:15 ` Jörn Engel
[not found] ` <efa6f5910611140541m302201e6t4e84551b75e79611@mail.gmail.com>
2006-11-14 13:56 ` Jörn Engel
2006-11-14 18:23 ` Andreas Dilger
2006-11-14 15:19 ` phillip
2006-11-14 18:19 ` Andreas Dilger
2006-11-14 0:15 ` Josef Sipek
2006-11-14 0:59 ` Bryan Henderson
2006-11-14 1:02 ` Theodore Tso
2006-11-14 11:21 ` Al Boldi
2006-11-14 14:25 ` Theodore Tso
2006-11-14 15:43 ` Al Boldi
2006-11-14 15:46 ` Matthew Wilcox [this message]
2006-11-14 16:59 ` Al Boldi
2006-11-14 17:27 ` Matthew Wilcox
2006-11-14 17:55 ` Theodore Tso
2006-11-14 18:23 ` Al Boldi
2006-11-14 14:30 ` phillip
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=20061114154630.GB19143@parisc-linux.org \
--to=matthew@wil.cx \
--cc=a1426z@gawab.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.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).