linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Tomas <alex@clusterfs.com>
To: Werner Almesberger <werner@almesberger.net>
Cc: Suparna Bhattacharya <suparna@in.ibm.com>,
	Mingming Cao <cmm@us.ibm.com>,
	Badari Pulavarty <pbadari@us.ibm.com>,
	ext2-devel <ext2-devel@lists.sourceforge.net>,
	linux-fsdevel@vger.kernel.org, Alex Tomas <alex@clusterfs.com>,
	abiss-general@lists.sourceforge.net
Subject: Re: Reviewing ext3 improvement patches (delalloc, mballoc, extents)
Date: Mon, 14 Mar 2005 18:43:02 +0300	[thread overview]
Message-ID: <m3k6oaxmgp.fsf@bzzz.home.net> (raw)
In-Reply-To: <20050314120240.K12802@almesberger.net> (Werner Almesberger's message of "Mon, 14 Mar 2005 12:02:40 -0300")

>>>>> Werner Almesberger (WA) writes:

 WA> Do you plan to reserve space as "blocks, somewhere", or as "these
 WA> specific on-disk locations" ? In ABISS, we did something of the
 WA> latter kind (in order to make large contiguous allocations also on
 WA> FAT), and it turned out to be a big mess, because ABISS needed too
 WA> much support from the file system driver. So we just scrapped that
 WA> bit :-)

I see no reason to reserve specific block in ->prepare/->commit in
delayed allocation case. We already do this with reservation.
The sole point of delayed allocation is to allocate many blocks at once:
to minimize fragmentation, to decrease allocator involvement, to avoid
allocation at all if the file gets truncated quickly.

 WA> The main parts: we added a new page flag, PG_delalloc, which
 WA> basically tells everyone to stay away from that page. There are
 WA> two purposes: (a) to make sure no allocation happens unless
 WA> explicitly requested, and (b) prevent the page from being written
 WA> back while it is still in ABISS' playout buffer. The reason for
 WA> (b) is that the page gets locked during writeback, which could
 WA> cause delays if the ABISS-using application then decides to
 WA> access the page.

locked during writeback? PG_writeback should be used instead of PG_locked.


thanks, Alex



-------------------------------------------------------
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

  reply	other threads:[~2005-03-14 15:43 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 [this message]
2005-03-14 16:37             ` 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
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=m3k6oaxmgp.fsf@bzzz.home.net \
    --to=alex@clusterfs.com \
    --cc=abiss-general@lists.sourceforge.net \
    --cc=cmm@us.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=pbadari@us.ibm.com \
    --cc=suparna@in.ibm.com \
    --cc=werner@almesberger.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 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).