From: Rich Altmaier <richa@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] CONFIG_IA64_PAGE_SIZE
Date: Thu, 18 Jan 2001 20:43:06 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005085@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005077@msgid-missing>
I very much like larger page sizes for their performance boosts,
typically the VM efficiency helps both code+data allocation and
helps IO operation setup/teardown.
However be aware of one significant downside to larger page sizes,
for workloads involving a large number of small processes.
Suppose you fire up 1000 processes on a system, then the
additional physical memory consumption is significant.
I actually don't know the correct calculation but guesstimate
that per-process data structures which increase in size
include kernel stack, task struct, each shared lib data segment,
user data segment. If the pagesize is increased from 4K to 64K,
then 4 such elements yield 60K*4*1000 processes = 240Mbyte.
Some customers do complain about this (and I tell them to buy
more memory and enjoy the performance).
Thanks, Rich
>
>
> On Thu, Jan 18, 2001 at 09:55:32AM -0800, Broadfoot, KenX wrote:
> >
> > Anyone in the know,
> >
> > I am using a 16KB page size for my Lion systems.
> >
> > Under the help section of make menuconfig is says:
> >
> > 4KB best for ia32
> >
> > 8KB best for ia64
> >
> > 16KB best for ia64
> >
> > 64KB Not for Itanium
> >
> >
> > I just want to know what is the gain or loss if I used 8KB instead of 16KB
> > page size.
> >
> > Also why is the 64KB page size bad for Itanium?
> >
> > Thanks.
> >
> > --ken
> >
next prev parent reply other threads:[~2001-01-18 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-18 17:55 [Linux-ia64] CONFIG_IA64_PAGE_SIZE Broadfoot, KenX
2001-01-18 18:14 ` David Mosberger
2001-01-18 18:21 ` Don Dugger
2001-01-18 18:31 ` David Mosberger
2001-01-18 20:43 ` Rich Altmaier [this message]
2001-01-18 21:53 ` Don Dugger
2001-01-19 1:43 ` David Mosberger
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-105590693005085@msgid-missing \
--to=richa@engr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.