linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Hugh Dickins <hugh@veritas.com>,
	Andrea Arcangeli <andrea@suse.de>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch][rfc] remove ZERO_PAGE?
Date: Fri, 27 Jul 2007 08:21:54 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.0.999.0707270811320.3442@woody.linux-foundation.org> (raw)
In-Reply-To: <20070727055406.GA22581@wotan.suse.de>


On Fri, 27 Jul 2007, Nick Piggin wrote:
> 
> What numbers, though? I can make up benchmarks to show that ZERO_PAGE
> sucks just as much. The problem I don't think is finding a situatoin that
> improves without it (we have an extreme case where the Altix livelocked)
> but to get confidence that nothing is going to blow up.

Well, the Altix livelock, for example, would seem to be simply because 
setting up the ZERO_PAGE is so much *faster* that it makes it easier to 
create humongous processes etc so quickly that you don't have time for 
them to be interrupted at setup time.

Is that the "fault" of ZERO_PAGE? Sure. But still..

> > Last time this came up, the logic behind wanting to remove the zero page 
> > was all screwed up, and it was all based on totally broken premises. So I 
> > really want somethign else than just "I don't like it".
> 
> I thought that last time this came up you thought it might be good to
> try out in -mm initially.

I was more thinking about all the churn that we got due to the reference 
counting stuff. That was pretty painful, and removing ZERO_PAGE wasn't the 
right answer then either.

> OK, well what numbers would you like to see? I can always try a few
> things.

Kernel builds with/without this? If the page faults really are that big a 
deal, this should all be visible.

		Linus

--
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>

  reply	other threads:[~2007-07-27 15:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-27  2:19 Nick Piggin
2007-07-27  5:29 ` Linus Torvalds
2007-07-27  5:54   ` Nick Piggin
2007-07-27 15:21     ` Linus Torvalds [this message]
2007-07-30  3:08       ` Nick Piggin
2007-07-30  3:45         ` Linus Torvalds
2007-07-30  3:56           ` Linus Torvalds
2007-07-30  4:35             ` Nick Piggin
2007-07-30  4:30           ` Nick Piggin
2007-07-27 15:59 ` Hugh Dickins
2007-07-30 13:52 ` Luiz Fernando N. Capitulino
2007-07-30 18:57   ` Andrew Morton
2007-07-30 22:39     ` J. Bruce Fields
2007-07-30 23:09       ` Andrew Morton
2007-07-31  0:03         ` Luiz Fernando N. Capitulino
2007-08-01  1:47       ` Nick Piggin
2007-08-01  1:53         ` J. Bruce Fields
2007-08-01  2:19           ` Luiz Fernando N. Capitulino
2007-08-01  3:03             ` J. Bruce Fields
2007-08-02  4:37             ` J. Bruce Fields
2007-08-03  1:40               ` Neil Brown
2007-08-01  2:17         ` Luiz Fernando N. Capitulino

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=alpine.LFD.0.999.0707270811320.3442@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=andrea@suse.de \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    /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