public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: pgd_free, pmd_free, and pte_free trapping memory.
Date: Tue, 16 Mar 2004 15:34:01 +0000	[thread overview]
Message-ID: <20040316153401.A1335@infradead.org> (raw)
In-Reply-To: <20040316112424.GA20203@lnx-holt>

On Tue, Mar 16, 2004 at 09:24:55AM -0600, Robin Holt wrote:
> I have a kernel with these ripped out.  I have run one simple Aim7 run
> on a 32P system.  The performance fell in the noise range of a normal
> Aim7 run.  Is this a good test to run?  Should I focus on any specific
> benchmark, or run a suite?

I'm not actually sure.  You could ask Ingo Molnar who implemented both
the per-cpu pages and ripped out the x86 quicklists if I remember correctly.

Ingo, any idea on how to benchmark that kind of thing best?

> > That's less code and thus less complexity which is always good.  Now if
> > the pre-zeroing actually makes a difference we might have to keep small
> > pre-zeroed list around, but I doubt this is really good idea (or even
> > nessecary)
> 
> The page zeroing costs 4uSec per page (I believe that is the number).
> With a typical fork taking approx 40 pages, that should be felt during
> an Aim7 run.  It looks like caches are masking some of that out.

OTOH you have more pages avalilable, the real per-cpu pages have a better
cache locality than the quicklists, the kernel has a smaller icache footprint,
etc..

  parent reply	other threads:[~2004-03-16 15:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 11:24 pgd_free, pmd_free, and pte_free trapping memory Robin Holt
2004-03-16 14:48 ` Christoph Hellwig
2004-03-16 15:24 ` Robin Holt
2004-03-16 15:34 ` Christoph Hellwig [this message]
2004-03-17 12:27 ` Robin Holt
2004-03-17 16:20 ` Jack Steiner
2004-03-17 16:53 ` Christoph Hellwig
2004-03-17 17:10 ` David Mosberger
2004-03-17 20:33 ` Jack Steiner

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=20040316153401.A1335@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-ia64@vger.kernel.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