From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: cmm@us.ibm.com, tytso@mit.edu, adilger@sun.com,
linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Group meta-data blocks together.
Date: Mon, 19 May 2008 15:27:52 +0530 [thread overview]
Message-ID: <20080519095752.GA2762@skywalker> (raw)
In-Reply-To: <482C617B.8090909@redhat.com>
On Thu, May 15, 2008 at 11:14:51AM -0500, Eric Sandeen wrote:
> Aneesh Kumar K.V wrote:
> > On Thu, May 15, 2008 at 09:23:59PM +0530, Aneesh Kumar K.V wrote:
> >> 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.
> >>
> >
> > The result can be found at
> >
> > http://www.radian.org/~kvaneesh/ext4/meta-group/
>
> Out of curiosity, do you have graphs similar to
> http://www.radian.org/~kvaneesh/ext4/meta-group/ext4-noextents-metagroup.png
>
> before and after your change?
http://www.radian.org/~kvaneesh/ext4/meta-group/exp1/
-aneesh
next prev parent reply other threads:[~2008-05-19 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-15 15:53 [PATCH] ext4: Use inode preallocation with -o noextents Aneesh Kumar K.V
2008-05-15 15:53 ` [PATCH] ext4: Group meta-data blocks together Aneesh Kumar K.V
2008-05-15 16:06 ` Aneesh Kumar K.V
2008-05-15 16:14 ` Eric Sandeen
2008-05-15 16:38 ` Aneesh Kumar K.V
2008-05-19 9:57 ` Aneesh Kumar K.V [this message]
2008-05-19 15:45 ` Eric Sandeen
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=20080519095752.GA2762@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--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 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.