From: Nick Piggin <npiggin@suse.de>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: "Kleen, Andi" <andi.kleen@intel.com>,
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: Thu, 5 Aug 2010 20:57:26 +1000 [thread overview]
Message-ID: <20100805105726.GB5683@amd> (raw)
In-Reply-To: <1280911823.2125.35.camel@ymzhang.sh.intel.com>
On Wed, Aug 04, 2010 at 04:50:23PM +0800, Zhang, Yanmin wrote:
> On Wed, 2010-08-04 at 09:06 +0100, Kleen, Andi wrote:
> > > > 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)
> I ported ext2 part to ext3. aim7 testing on Nehalem EX 4 socket machine
> shows the regression disappears.
Thanks, this looks fine I'll port several more of the popular
filesystems over asap.
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@suse.de>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: "Kleen, Andi" <andi.kleen@intel.com>,
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: Thu, 5 Aug 2010 20:57:26 +1000 [thread overview]
Message-ID: <20100805105726.GB5683@amd> (raw)
In-Reply-To: <1280911823.2125.35.camel@ymzhang.sh.intel.com>
On Wed, Aug 04, 2010 at 04:50:23PM +0800, Zhang, Yanmin wrote:
> On Wed, 2010-08-04 at 09:06 +0100, Kleen, Andi wrote:
> > > > 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)
> I ported ext2 part to ext3. aim7 testing on Nehalem EX 4 socket machine
> shows the regression disappears.
Thanks, this looks fine I'll port several more of the popular
filesystems over asap.
--
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-05 10:57 UTC|newest]
Thread overview: 20+ 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 ` scalability investigation: Where can I get your latest patches? Zhang, Yanmin
2010-08-04 1:04 ` Zhang, Yanmin
2010-08-04 7:21 ` Kleen, Andi
2010-08-04 7:21 ` Kleen, Andi
2010-08-04 7:58 ` Zhang, Yanmin
2010-08-04 7:58 ` Zhang, Yanmin
2010-08-04 8:06 ` Kleen, Andi
2010-08-04 8:50 ` Zhang, Yanmin
2010-08-04 8:50 ` Zhang, Yanmin
2010-08-05 10:57 ` Nick Piggin [this message]
2010-08-05 10:57 ` Nick Piggin
2010-08-05 10:55 ` Nick Piggin
2010-08-09 2:11 ` Zhang, Yanmin
2010-08-09 2:11 ` Zhang, Yanmin
2010-08-09 3:20 ` Zhang, Yanmin
2010-08-09 3:20 ` Zhang, Yanmin
2010-08-05 11:44 ` Nick Piggin
2010-08-05 11:44 ` Nick Piggin
2010-08-09 2:36 ` Zhang, Yanmin
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=20100805105726.GB5683@amd \
--to=npiggin@suse.de \
--cc=alex.shi@intel.com \
--cc=andi.kleen@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 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.