From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] page size > 16KB
Date: Wed, 12 Mar 2003 18:07:30 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709806064@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709806057@msgid-missing>
>>>>> On Wed, 12 Mar 2003 09:49:41 -0800, Jesse Barnes <jbarnes@sgi.com> said:
Jesse> Really? What sorts of benchmarks have you done that show
Jesse> large improvements? I ask because I can think of a few that
Jesse> might benefit, but have yet to see real world improvements of
Jesse> any significance, so I'm curious.
Anything that's hurt significantly by TLB pressure will gain
signifcantly. Even apps that stream through memory (e.g., STREAMS)
can see significant gains. Other advantages are more reproducible
results (since you're effectively getting some page coloring for
"free") and much larger user virtual address space.
However, the part that really surprised me is how little ordinary apps
seem to suffer from the higher page-fault latency and increased
internal fragmentation. I don't recall the exact numbers, but even a
kernel compile ran almost as fast with 64KB page size as with 16KB
page size.
If you know of a real-world application that suffers significantly
from 64KB page size, I'd like to hear about it.
--david
next prev parent reply other threads:[~2003-03-12 18:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 16:38 [Linux-ia64] page size > 16KB Jan Schreckenbach
2003-03-12 16:55 ` Grant Grundler
2003-03-12 17:07 ` n0ano
2003-03-12 17:40 ` David Mosberger
2003-03-12 17:46 ` David Mosberger
2003-03-12 17:49 ` Jesse Barnes
2003-03-12 18:07 ` David Mosberger [this message]
2003-03-12 18:08 ` Grant Grundler
2003-03-12 18:24 ` Jesse Barnes
2003-03-12 19:51 ` Mario Smarduch
2003-03-13 18:05 ` David Mosberger
2003-03-13 20:44 ` Mario Smarduch
2003-03-14 12:33 ` Jan Schreckenbach
2003-03-14 15:51 ` Chen, Kenneth W
2003-03-14 17:33 ` Jesse Barnes
2003-03-14 18:00 ` Mario Smarduch
2003-03-14 18:17 ` Grant Grundler
2003-03-14 19:00 ` Jesse Barnes
2003-03-14 19:43 ` David Mosberger
2003-03-15 3:08 ` Seth, Rohit
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=marc-linux-ia64-105590709806064@msgid-missing \
--to=davidm@napali.hpl.hp.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