From: Andrea Arcangeli <andrea@novell.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
Andrew Morton <akpm@osdl.org>,
nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: Re: PG_zero
Date: Tue, 2 Nov 2004 20:39:01 +0100 [thread overview]
Message-ID: <20041102193901.GO3571@dualathlon.random> (raw)
In-Reply-To: <41879145.7090309@shadowen.org>
On Tue, Nov 02, 2004 at 01:53:09PM +0000, Andy Whitcroft wrote:
> I'll have a look out for the results, they should be around somewhere?
could you give an hint on which workload to use for the measurements?
> page for use. The colder the page the slower the system went.
this is expected. This is why I waste no more than 4k of cache for each
local-apic irq, and this is also why I don't waste any cache at all if
the zerolist is already full or the hot-cold list is empty (plus if
there are PG_zero pages in the hot-cold list since I cache PG_zere deep
down in the buddy, I don't waste any cache at all by refiling them into
the zero quicklist). Not sure if you were using the same design. Note
that idle zeroing is a worthless feature in my patch, I never intented
to implement it, I just happened to be able to implement it with a
trivial change so I did (and it can be disabled via sysctl). all the
important stuff are bugfixes and obsoleting the inefficient slab for pte
allocation and to create a superset of the pte_quicklist in 2.4 that is
missing in 2.6 by mistake.
Note that I'm keeping track of hot and cold cache for the zerolist too.
Plus I can disable the idle zeroing and still I will be able to cache
zero information in O(1) (so then caching zero will be zerocost, plus
I'll keep track of the hottest zero page, and the coldest one).
next prev parent reply other threads:[~2004-11-02 19:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 14:10 PG_zero Andrea Arcangeli
2004-10-30 21:07 ` PG_zero Andrew Morton
2004-10-30 22:45 ` PG_zero Andrea Arcangeli
2004-10-31 15:35 ` PG_zero Martin J. Bligh
2004-11-01 21:57 ` PG_zero Andrea Arcangeli
2004-11-01 22:05 ` PG_zero Martin J. Bligh
2004-11-02 3:41 ` PG_zero William Lee Irwin III
2004-10-31 15:17 ` PG_zero Martin J. Bligh
2004-11-02 13:53 ` PG_zero Andy Whitcroft
2004-11-02 19:39 ` Andrea Arcangeli [this message]
2004-11-01 17:26 ` PG_zero Nick Piggin
2004-11-01 18:03 ` PG_zero Martin J. Bligh
2004-11-01 22:34 ` PG_zero Andrea Arcangeli
2004-11-01 23:47 ` PG_zero Martin J. Bligh
2004-11-02 1:47 ` PG_zero Nick Piggin
2004-11-02 2:21 ` PG_zero Andrea Arcangeli
2004-11-02 2:54 ` PG_zero Nick Piggin
2004-11-02 15:42 ` PG_zero Martin J. Bligh
2004-11-02 19:50 ` PG_zero Andrea Arcangeli
2004-11-02 22:41 ` PG_zero Martin J. Bligh
2004-11-03 1:26 ` PG_zero Andrea Arcangeli
2004-11-02 21:09 ` PG_zero Andrew Morton
2004-11-02 21:56 ` PG_zero Andrea Arcangeli
2004-11-02 22:41 ` PG_zero Martin J. Bligh
2004-11-03 1:09 ` PG_zero Andrea Arcangeli
2004-11-03 1:18 ` PG_zero Martin J. Bligh
2004-11-03 1:23 ` PG_zero Nick Piggin
2004-11-03 2:05 ` PG_zero Andrea Arcangeli
2004-11-03 11:53 ` PG_zero Andrea Arcangeli
2004-11-03 12:10 ` PG_zero Pavel Machek
2004-11-01 22:24 ` PG_zero Andrea Arcangeli
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=20041102193901.GO3571@dualathlon.random \
--to=andrea@novell.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=nickpiggin@yahoo.com.au \
/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