linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Tomas <alex@clusterfs.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: David Chinner <dgc@sgi.com>, Alex Tomas <alex@clusterfs.com>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] delayed allocation for ext4
Date: Sat, 23 Dec 2006 22:15:43 +0300	[thread overview]
Message-ID: <m3vek2todc.fsf@bzzz.home.net> (raw)
In-Reply-To: <20061223092718.GA26276@infradead.org> (Christoph Hellwig's message of "Sat\, 23 Dec 2006 09\:27\:18 +0000")

>>>>> Christoph Hellwig (CH) writes:

 CH> Note that recording delayed alloc state at a page granularity in addition
 CH> to just the buffer heads has a lot of advantages aswell and would help
 CH> xfs, too.  But I think it makes a lot more sense to record it as a radix
 CH> tree tag to speed up the gang lookups for delalloc conversion.

please, exaplein about radix tree tag. in ext4-delalloc I use this
bit the only way - to avoid multiple reservation space for same
page. I guess you need to find non-allocated pages. probably to
flush them and update number of reserved blocks in case of -ENOSPC?

thanks, Alex

  reply	other threads:[~2006-12-23 19:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22 20:20 [RFC] delayed allocation for ext4 Alex Tomas
2006-12-22 20:23 ` [RFC] booked-page-flag.patch Alex Tomas
2006-12-22 20:25 ` [RFC] ext4-block-reservation.patch Alex Tomas
2006-12-23 22:40   ` Andrew Morton
2006-12-23 22:47     ` Alex Tomas
2006-12-22 20:28 ` [RFC] ext4-delayed-allocation.patch Alex Tomas
2006-12-23 22:59   ` Andrew Morton
2007-01-12 14:45   ` Valerie Clement
2007-01-12 14:52     ` Alex Tomas
2006-12-23  3:31 ` [RFC] delayed allocation for ext4 David Chinner
2006-12-23  9:27   ` Christoph Hellwig
2006-12-23 19:15     ` Alex Tomas [this message]
2006-12-29  2:50     ` David Chinner
2006-12-23 19:09   ` Alex Tomas
2006-12-29  2:52     ` David Chinner
2006-12-29  4:56       ` Alex Tomas

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=m3vek2todc.fsf@bzzz.home.net \
    --to=alex@clusterfs.com \
    --cc=dgc@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).