From: "Kleen, Andi" <andi.kleen@intel.com>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: Nick Piggin <npiggin@suse.de>, "Shi, Alex" <alex.shi@intel.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: RE: scalability investigation: Where can I get your latest patches?
Date: Wed, 4 Aug 2010 09:06:18 +0100 [thread overview]
Message-ID: <F4DF93C7785E2549970341072BC32CD78D8FC0CC@irsmsx503.ger.corp.intel.com> (raw)
In-Reply-To: <1280908717.2125.33.camel@ymzhang.sh.intel.com>
> > I believe the latest version of Nick's patchkit has a likely fix for
> that.
> >
> > http://git.kernel.org/?p=linux/kernel/git/npiggin/linux-
> npiggin.git;a=commitdiff;h=9edd35f9aeafc8a5e1688b84cf4488a94898ca45
>
> Thanks Andi. The patch has no ext3 part.
Good point. But perhaps the ext2 patch can be adapted. The ACL code
should be similar in ext2 and ext3 (and 4)
-Andi
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-08-04 8:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1278579387.2096.889.camel@ymzhang.sh.intel.com>
[not found] ` <20100720031201.GC21274@amd>
2010-08-04 1:04 ` Zhang, Yanmin
2010-08-04 7:21 ` Kleen, Andi
2010-08-04 7:58 ` Zhang, Yanmin
2010-08-04 8:06 ` Kleen, Andi [this message]
2010-08-04 8:50 ` Zhang, Yanmin
2010-08-05 10:57 ` Nick Piggin
2010-08-05 10:55 ` Nick Piggin
2010-08-09 2:11 ` Zhang, Yanmin
2010-08-09 3:20 ` Zhang, Yanmin
2010-08-05 11:44 ` Nick Piggin
2010-08-09 2:36 ` Zhang, Yanmin
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=F4DF93C7785E2549970341072BC32CD78D8FC0CC@irsmsx503.ger.corp.intel.com \
--to=andi.kleen@intel.com \
--cc=alex.shi@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=yanmin_zhang@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox