From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] CONFIG_IA64_PAGE_SIZE
Date: Fri, 19 Jan 2001 01:43:44 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005087@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005077@msgid-missing>
>>>>> On Thu, 18 Jan 2001 12:43:06 -0800, Rich Altmaier <richa@engr.sgi.com> said:
Rich> However be aware of one significant downside to larger page
Rich> sizes, for workloads involving a large number of small
Rich> processes. Suppose you fire up 1000 processes on a system,
Rich> then the additional physical memory consumption is
Rich> significant. I actually don't know the correct calculation
Rich> but guesstimate that per-process data structures which
Rich> increase in size include kernel stack, task struct, each
Rich> shared lib data segment, user data segment. If the pagesize
Rich> is increased from 4K to 64K, then 4 such elements yield
Rich> 60K*4*1000 processes = 240Mbyte.
The minimum task size was an important consideration in the design of
IA-64 Linux. As Don pointed out, the process data structure is at
least 32KB no matter what page size is in use (to avoid stack
overflow), so this really makes a difference only when the page size
is 64KB.
However, the real biggie are the page tables. Even the smallest task
needs at the least three page table pages, so here the page size can
have a big impact.
Rich> Some customers do complain about this (and I tell them to buy
Rich> more memory and enjoy the performance).
Good answer! ;-)
--david
prev parent reply other threads:[~2001-01-19 1: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
2001-01-18 21:53 ` Don Dugger
2001-01-19 1:43 ` David Mosberger [this message]
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-105590693005087@msgid-missing \
--to=davidm@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