From: Theodore Ts'o <tytso@mit.edu>
To: T Makphaibulchoke <tmac@hp.com>,
viro@zeniv.linux.org.uk, adilger.kernel@dilger.ca,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ext4@vger.kernel.org, tmakph@gmail.com, aswin@hp.com
Subject: Re: [PATCH 0/2] ext4: increase mbcache scalability
Date: Thu, 18 Jul 2013 12:33:01 -0400 [thread overview]
Message-ID: <20130718163301.GB12727@thunk.org> (raw)
In-Reply-To: <20130718163024.GA12727@thunk.org>
On Thu, Jul 18, 2013 at 12:30:24PM -0400, Theodore Ts'o wrote:
> On Wed, Jul 17, 2013 at 06:55:10PM -0600, T Makphaibulchoke wrote:
> > This patch intends to improve the scalability of an ext4 filesystem by
> > introducing higher degree of parallelism to the usages of its mb_cache and
> > mb_cache_entries.
> >
> > ...
> >
> > fs/ext4/ext4.h | 1 +
> > fs/ext4/super.c | 8 ++
> > fs/ext4/xattr.c | 41 +++++---
> > fs/ext4/xattr.h | 3 +
> > fs/mbcache.c | 432 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------
> > include/linux/mbcache.h | 5 +
> > 6 files changed, 385 insertions(+), 105 deletions(-)
> >
>
> I see the diff stats, but there was no patch attached to your message.
> Could you please resend the patch to the linux-ext4 list?
Never mind, I see them now. I didn't notice this was a 0/2 message,
and since you are apparently using an old versio of git which doesn't
enable --thread by default (or you have a git config setting which
disables the use of mail threading), I didn't see the patches chained
to the message.
Sorry for being confused,
- Ted
next prev parent reply other threads:[~2013-07-18 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 0:55 [PATCH 0/2] ext4: increase mbcache scalability T Makphaibulchoke
2013-07-18 16:30 ` Theodore Ts'o
2013-07-18 16:33 ` Theodore Ts'o [this message]
2013-07-29 10:08 ` Thavatchai Makphaibulchoke
2013-07-18 0:55 T Makphaibulchoke
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=20130718163301.GB12727@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=aswin@hp.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmac@hp.com \
--cc=tmakph@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).