From: Werner Almesberger <werner@almesberger.net>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: abiss-general@lists.sourceforge.net,
Alex Tomas <alex@clusterfs.com>,
cmm@us.ibm.com, ext2-devel <ext2-devel@lists.sourceforge.net>,
linux-fsdevel@vger.kernel.org, pbadari@us.ibm.com,
Suparna Bhattacharya <suparna@in.ibm.com>
Subject: Re: Reviewing ext3 improvement patches (delalloc, mballoc, extents)
Date: Mon, 14 Mar 2005 21:42:53 -0300 [thread overview]
Message-ID: <20050314214253.P12802@almesberger.net> (raw)
In-Reply-To: <OFBA882AB7.0FC15B10-ON88256FC4.0078329F-88256FC4.007AF3E0@us.ibm.com>; from hbryan@us.ibm.com on Mon, Mar 14, 2005 at 02:23:04PM -0800
Bryan Henderson wrote:
> I think "reservation" is wrong for one of them and anyone using it that
> way should stop.
Hehe, start with ext3 :-)
> I believe the common terminology is:
Sounds reasonable. The thing with "reservation" is that people use
it in daily life with all kinds of meanings, and often with the
object of the reservation, e.g. "reserve a seat" (typically a
specific seat), "reserve some time" (often not a specific interval),
or "reserve a table" (at a restaurant, you don't know which one,
but the restaurant staff does).
To muddy the issue further, reservations can be more or less firm.
E.g. if we "reserve" the next hundred blocks, so that allocation is
contiguous, we may want to be able to take them away if some other
file needs them. On the other hand, if storage is already committed,
but just not on disk yet, that reservation shouldn't be revokable.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina werner@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-15 0:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 8:33 Reviewing ext3 improvement patches (delalloc, mballoc, extents) Suparna Bhattacharya
2005-03-03 9:40 ` Andreas Dilger
2005-03-03 22:10 ` Theodore Ts'o
2005-03-03 22:30 ` Alex Tomas
2005-03-04 11:13 ` Suparna Bhattacharya
2005-03-04 12:29 ` Alex Tomas
2005-03-04 18:25 ` [Ext2-devel] " Andreas Dilger
2005-03-04 1:12 ` [Ext2-devel] " Badari Pulavarty
2005-03-04 1:46 ` Mingming Cao
2005-03-04 3:26 ` Suparna Bhattacharya
2005-03-14 8:36 ` Werner Almesberger
2005-03-14 9:04 ` Suparna Bhattacharya
2005-03-14 15:02 ` Werner Almesberger
2005-03-14 15:43 ` Alex Tomas
2005-03-14 16:37 ` [Ext2-devel] " Werner Almesberger
2005-03-14 17:13 ` Alex Tomas
2005-03-15 0:28 ` Werner Almesberger
2005-03-14 22:23 ` Bryan Henderson
2005-03-15 0:42 ` Werner Almesberger [this message]
2005-03-15 21:59 ` Bryan Henderson
2005-03-04 11:30 ` [Ext2-devel] " Alex Tomas
2005-03-04 15:02 ` Alex Tomas
2005-03-13 14:41 ` Delayed alloc for ordered-mode Suparna Bhattacharya
2005-03-13 19:32 ` Badari Pulavarty
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=20050314214253.P12802@almesberger.net \
--to=werner@almesberger.net \
--cc=abiss-general@lists.sourceforge.net \
--cc=alex@clusterfs.com \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=hbryan@us.ibm.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=suparna@in.ibm.com \
/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).