From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andreas Dilger <adilger@sun.com>
Cc: sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [RFC PATCH] ext4: Group meta-data blocks together.
Date: Fri, 2 May 2008 23:42:33 +0530 [thread overview]
Message-ID: <20080502181233.GA12049@skywalker> (raw)
In-Reply-To: <20080502174901.GC2950@webber.adilger.int>
On Fri, May 02, 2008 at 10:49:01AM -0700, Andreas Dilger wrote:
> On Apr 29, 2008 16:27 +0530, Aneesh Kumar K.V wrote:
> > I haven't yet tested this. Let me know what you think.
> >
> > -aneesh
> >
> > This adds a per inode meta-block prealloc space from which
> > meta-data block requests are served. This help in making
> > sure meta-data block are closer. This is needed to speedup
> > unlink of the file. Any new prealloc space is allocated near
> > the goal block specified. The goal block is the last block
> > allocated for the file. So we don't keep the data-block and
> > meta-data block far apart.
>
> Does this code use the mballoc "group allocator" mechanism that it
> already uses for small files? It would be convenient to re-use
> this code by creating a "metadata allocation group" instead of creating
> another mechanism to aggregate small IO allocations.
>
That is mostly what it does. Except that the allocation space is hanging
from the inode rather than per-cpu.
-aneesh
prev parent reply other threads:[~2008-05-02 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 10:57 [RFC PATCH] ext4: Group meta-data blocks together Aneesh Kumar K.V
2008-04-29 20:19 ` Eric Sandeen
2008-04-30 10:07 ` Aneesh Kumar K.V
2008-05-02 17:49 ` Andreas Dilger
2008-05-02 18:12 ` Aneesh Kumar K.V [this message]
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=20080502181233.GA12049@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.