From: Nick Piggin <npiggin@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
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: Mon, 30 Jul 2007 06:35:28 +0200 [thread overview]
Message-ID: <20070730043528.GC7222@wotan.suse.de> (raw)
In-Reply-To: <alpine.LFD.0.999.0707292049420.4161@woody.linux-foundation.org>
On Sun, Jul 29, 2007 at 08:56:54PM -0700, Linus Torvalds wrote:
>
>
> On Sun, 29 Jul 2007, Linus Torvalds wrote:
> >
> > I'd love to hear "here's a real-life load, and yes, the ZERO_PAGE logic
> > really does hurt more than it helps, it's time to remove it". At that
> > point I'll happily apply the patch.
>
> Btw, in the absense of that, I'd at least like to hear an acknowledgement
> that the complexity isn't worth it, and that what used to work fine was
> broken because the reference counting overhead gets us on large-scale
> machines.
>
> IOW, I certainly like removing lines of code. In that sense I _love_ that
> patch. I really just react negatively because I really think you first set
> ZERO_PAGE up to fail.
>
> So even if you cannot find a load where this all matters, at least point
> to commit b5810039a54e5babf428e9a1e89fc1940fabff11 (or exactly whichever
> one it was that started ref-counting ZERO_PAGE) and blame *that* one,
> rather than blaming ZERO_PAGE for the problem.
OK, as a patch, the changelog could be improved. But I state that
complexity isn't worth it as "ZERO_PAGE appears to be a false optimisation".
> It has served us well for fifteen years, we shouldn't blame it for
> problems that came from elsewhere.
Can it still serve us well, though? This is what I would really like to talk
about, and I guess would decide whether we again special case the refcounting
or remove it completely. I'm happy to do either (although I do *hope* that it
can be removed, for complexity's sake).
--
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:[~2007-07-30 4:35 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
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 [this message]
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=20070730043528.GC7222@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andrea@suse.de \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.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