From: ebiederm@xmission.com (Eric W. Biederman)
To: Linus Torvalds <torvalds@osdl.org>
Cc: Anton Ertl <anton@mips.complang.tuwien.ac.at>,
linux-kernel@vger.kernel.org
Subject: Re: Page Colouring (was: 2.6.0 Huge pages not working as expected)
Date: 27 Dec 2003 16:31:22 -0700 [thread overview]
Message-ID: <m1smj596t1.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0312271245370.2274@home.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
> On Sat, 27 Dec 2003, Anton Ertl wrote:
> >
> > And you probably mean "repeatable every time". Ok, then a random
> > scheme has, by your definition, no pathological worst case. I am not
> > sure that this is a consolation when I happen upon one of its
> > unpredictable and unrepeatable worst cases.
>
> Those "unpredictable" cases are so exceedingly rare that they aren't worth
> worrying about.
They show up a lot in benchmarks which makes the something
to worry about. Even if real world applications don't show
the same behavior. Of course it is stupid to tune machines
to the benchmarks but...
> Basically: prove me wrong. People have tried before. They have failed.
> Maybe you'll succeed. I doubt it, but hey, I'm not stopping you.
For anyone taking you up on this I'd like to suggest two possible
directions.
1) Increasing PAGE_SIZE in the kernel.
2) Creating zones for the different colors. Zones were not
implemented last time, this was tried.
Both of those should be minimal impact to the complexity
of the current kernel.
I don't know where we will wind up but the performance variation's
caused by cache conflicts in today's applications are real, and easily
measurable. Giving the growing increase in performance difference
between CPUs and memory Amdahl's Law shows this will only grow
so I think this is worth looking at.
Eric
next prev parent reply other threads:[~2003-12-27 23:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <179fV-1iK-23@gated-at.bofh.it>
[not found] ` <179IS-1VD-13@gated-at.bofh.it>
2003-12-27 20:21 ` Anton Ertl
2003-12-27 20:56 ` Linus Torvalds
2003-12-27 23:31 ` Eric W. Biederman [this message]
2003-12-27 23:50 ` William Lee Irwin III
2003-12-28 1:09 ` David S. Miller
2003-12-28 4:53 ` Linus Torvalds
2003-12-28 16:39 ` William Lee Irwin III
2003-12-29 0:36 ` Mike Fedyk
2003-12-29 2:55 ` William Lee Irwin III
2003-12-29 4:09 ` Linus Torvalds
2003-12-29 6:52 ` William Lee Irwin III
2003-12-29 9:14 ` Linus Torvalds
2003-12-29 9:22 ` William Lee Irwin III
2003-12-29 9:33 ` Linus Torvalds
2003-12-29 10:23 ` William Lee Irwin III
2003-12-29 10:59 ` Mike Fedyk
2003-12-29 11:14 ` William Lee Irwin III
2003-12-30 2:00 ` Rusty Russell
2003-12-30 4:59 ` William Lee Irwin III
[not found] ` <20031229084304.GA31630@elte.hu>
2003-12-29 12:09 ` Ingo Molnar
2003-12-29 12:49 ` William Lee Irwin III
2003-12-29 20:02 ` Subpages (was: Page Colouring) Daniel Phillips
2003-12-29 20:15 ` Linus Torvalds
2003-12-29 21:11 ` Page Colouring (was: 2.6.0 Huge pages not working as expected) Eric W. Biederman
2003-12-29 21:35 ` Linus Torvalds
[not found] ` <17tHK-3K6-21@gated-at.bofh.it>
2003-12-28 17:17 ` Anton Ertl
[not found] <176UD-6vl-3@gated-at.bofh.it>
2003-12-26 21:48 ` Anton Ertl
2003-12-26 23:28 ` Linus Torvalds
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=m1smj596t1.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=anton@mips.complang.tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
Powered by JetHome