From: Robin Holt <holt@sgi.com>
To: "Roedel, Joerg" <Joerg.Roedel@amd.com>
Cc: Robin Holt <holt@sgi.com>, Jack Steiner <steiner@sgi.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
Yinghai Lu <yinghai@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Stable Maintainers <stable@kernel.org>
Subject: Re: [Patch] numa:x86_64: Cacheline aliasing makes for_each_populated_zone extremely expensive -V2.
Date: Thu, 19 Aug 2010 17:02:14 -0500 [thread overview]
Message-ID: <20100819220214.GI3043@sgi.com> (raw)
In-Reply-To: <20100819204256.GH3043@sgi.com>
> > I don't think this is stable material. It improves performance and does
> > not fix a bug. But I am not the one to decide this :-)
>
> The only reason I think it qualifies is we are talking about 0.8% of each
> cpus time. That means that on the 4096 cpu system, we are dedicating
> the equivalent of 32 cpus to just vmstat_update. That feels like it
Wrong! 0.08%, not 0.8% and therefore 3.2 cpus, not 32.
Sorry for the confusion,
Robin
next prev parent reply other threads:[~2010-08-19 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 16:56 [Patch] numa:x86_64: Cacheline aliasing makes for_each_populated_zone extremely expensive Robin Holt
2010-08-18 18:30 ` [Patch] numa:x86_64: Cacheline aliasing makes for_each_populated_zone extremely expensive -V2 Robin Holt
2010-08-19 17:30 ` Roedel, Joerg
2010-08-19 20:42 ` Robin Holt
2010-08-19 22:02 ` Robin Holt [this message]
2010-08-19 22:54 ` H. Peter Anvin
2010-08-20 13:58 ` Robin Holt
2010-08-20 15:03 ` Robin Holt
2010-08-20 16:16 ` H. Peter Anvin
2010-08-21 13:07 ` Robin Holt
2010-08-23 21:42 ` H. Peter Anvin
2010-08-25 11:08 ` Robin Holt
2010-08-25 18:56 ` H. Peter Anvin
2010-08-25 21:49 ` Yinghai Lu
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=20100819220214.GI3043@sgi.com \
--to=holt@sgi.com \
--cc=Joerg.Roedel@amd.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=stable@kernel.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/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).