From: Jack Steiner <steiner@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: pgd_free, pmd_free, and pte_free trapping memory.
Date: Wed, 17 Mar 2004 16:20:16 +0000 [thread overview]
Message-ID: <20040317162016.GB32491@sgi.com> (raw)
In-Reply-To: <20040316112424.GA20203@lnx-holt>
> >
> > Robin> The page zeroing costs 4uSec per page (I believe that is the
> > Robin> number). With a typical fork taking approx 40 pages, that
> > Robin> should be felt during an Aim7 run. It looks like caches are
> > Robin> masking some of that out.
> >
> > Try UP. Also, what if the page-size is 64KB? In any case, 4usec is a
> > lot.
>
> I got the 4uSec from Jack Steiner. I don't know if he tested it with
> 64KB pages. I will check.
I see the following times for the kernel "clearpage" routine. I run this
code in user space but I use the kernel assembly code for clearing pages.
AFAICT, the timing should be identical to running it in the kernel.
The test harness ensures that the timing is done with warm TLBs & cold
cache (data not in cpu caches):
3.1 usec 16K node local memory
6.1 usec 16K remote memory
12.5 usec 64K node local memory
24.5 usec 64K remote memory
I ran this on Itanium 2 1300MHz cpus. However, processor core speed does
not significantly affect timings since most time is spent waiting for
off chip memory access.
Also, timing will obviously vary across different platforms.
--
Thanks
Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
next prev parent reply other threads:[~2004-03-17 16:20 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
2004-03-17 12:27 ` Robin Holt
2004-03-17 16:20 ` Jack Steiner [this message]
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=20040317162016.GB32491@sgi.com \
--to=steiner@sgi.com \
--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