From: Hugh Dickins <hugh@veritas.com>
To: Dan Aloni <da-x@monatomic.org>
Cc: Andrea Arcangeli <andrea@suse.de>, Nick Piggin <npiggin@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
tee@sgi.com, holt@sgi.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [rfc] no ZERO_PAGE?
Date: Wed, 4 Apr 2007 16:03:15 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0704041553220.18202@blonde.wat.veritas.com> (raw)
In-Reply-To: <20070404144421.GA13762@localdomain>
On Wed, 4 Apr 2007, Dan Aloni wrote:
>
> To refine that example, you could replace the file with a large anonymous
> memory pool and a lot of swap space committed to it. In that case - with
> no ZERO_PAGE, would the kernel needlessly swap-out the zeroed pages?
> Perhaps it's an example too far-fetched to worth considering...
Nice point, not far-fetched, though I don't know whether it's worth
worrying about or not. Yes, as things stand, the kernel will
needlessly write them out to swap: because we're in the habit of
marking a writable pte as dirty, partly to save the processor (how
i386-centric am I being?) from having to do that work just after,
partly because of some race too ancient for me to know anything
about - do_no_page (though not the function in question here) says:
* This silly early PAGE_DIRTY setting removes a race
* due to the bad i386 page protection. But it's valid
* for other architectures too.
Maybe Nick will decide to not to mark the readfaults as dirty.
Hugh
next prev parent reply other threads:[~2007-04-04 15:03 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070329075805.GA6852@wotan.suse.de>
[not found] ` <Pine.LNX.4.64.0703291324090.21577@blonde.wat.veritas.com>
[not found] ` <20070330024048.GG19407@wotan.suse.de>
2007-04-04 3:37 ` Nick Piggin
2007-04-04 9:45 ` Hugh Dickins
2007-04-04 10:24 ` Nick Piggin
2007-04-04 12:27 ` Andrea Arcangeli
2007-04-04 13:55 ` Dan Aloni
2007-04-04 14:14 ` Andrea Arcangeli
2007-04-04 14:44 ` Dan Aloni
2007-04-04 15:03 ` Hugh Dickins [this message]
2007-04-04 15:34 ` Andrea Arcangeli
2007-04-04 15:41 ` Hugh Dickins
2007-04-04 16:07 ` Andrea Arcangeli
2007-04-04 16:14 ` Linus Torvalds
2007-04-04 15:27 ` Andrea Arcangeli
2007-04-04 16:15 ` Dan Aloni
2007-04-04 16:48 ` Andrea Arcangeli
2007-04-04 12:45 ` Hugh Dickins
2007-04-04 13:05 ` Andrea Arcangeli
2007-04-04 13:32 ` Hugh Dickins
2007-04-04 13:40 ` Andrea Arcangeli
2007-04-04 15:35 ` Linus Torvalds
2007-04-04 15:48 ` Andrea Arcangeli
2007-04-04 16:09 ` Linus Torvalds
2007-04-04 16:23 ` Andrea Arcangeli
2007-04-04 16:10 ` Hugh Dickins
2007-04-04 16:31 ` Andrea Arcangeli
2007-04-04 22:07 ` Valdis.Kletnieks
2007-04-04 16:32 ` Eric Dumazet
2007-04-04 17:02 ` Linus Torvalds
2007-04-04 19:15 ` Andrew Morton
2007-04-04 20:11 ` David Miller
2007-04-04 20:50 ` Andrew Morton
2007-04-05 2:03 ` Nick Piggin
2007-04-05 5:23 ` Andrea Arcangeli
2007-04-04 22:05 ` Valdis.Kletnieks
2007-04-05 0:27 ` Linus Torvalds
2007-04-05 1:25 ` Valdis.Kletnieks
2007-04-05 2:30 ` Nick Piggin
2007-04-05 5:37 ` William Lee Irwin III
2007-04-05 17:23 ` Valdis.Kletnieks
2007-04-05 4:47 ` Nick Piggin
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=Pine.LNX.4.64.0704041553220.18202@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=andrea@suse.de \
--cc=da-x@monatomic.org \
--cc=holt@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=tee@sgi.com \
--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
all inboxes | Powered by JetHome®