From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Eric W. Biederman" <ebiederm+eric@ccr.net>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
"Benjamin C.R. LaHaise" <blah@kvack.org>,
Daniel Blakeley <daniel@msc.cornell.edu>,
linux-mm@kvack.org
Subject: Re: Large memory system
Date: Tue, 9 Feb 1999 22:57:51 GMT [thread overview]
Message-ID: <199902092257.WAA05676@dax.scot.redhat.com> (raw)
In-Reply-To: <m17lts52v4.fsf@flinx.ccr.net>
Hi,
On 08 Feb 1999 09:31:11 -0600, ebiederm+eric@ccr.net (Eric W. Biederman)
said:
> Cool. We now have an idea that sounds possible.
> The only remaining question is how much of a performance hit would
> changing the contents of a pte around all of the time be?
Very little: there's the cost of the page invalidate (a couple of
cycles), plus the cost of the CPU refilling that tlb from the page
tables. It's completely lost in the noise compared to the cost of
transferring an entire page of data to/from user space.
> Every single page read/write syscall, as well as copying down to I/O
> bounce buffers sounds common enough that we probably would see a
> performance hit.
I doubt that it would be measurable.
> The other thing that happens is we start breaking assumptions about
> fixed limits based on architecture size. Things like the swap entry
> may need to be expanded.
The swap entry can probably stay completely independent; most people
with 8G of ram are going to be trying hard never to hit swap anyway. :)
Besides, we already have support for 16G of swap as things stand.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-02-09 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-30 13:36 Daniel Blakeley
1999-01-30 17:00 ` Benjamin C.R. LaHaise
1999-02-08 11:24 ` Stephen C. Tweedie
1999-02-08 15:31 ` Eric W. Biederman
1999-02-09 22:57 ` Stephen C. Tweedie [this message]
1999-02-01 15:59 ` Rik van Riel
1999-02-08 11:22 ` Stephen C. Tweedie
1999-02-08 20:33 Manfred Spraul
1999-02-10 14:25 ` Stephen C. Tweedie
1999-02-10 17:02 Manfred Spraul
1999-02-11 11:12 ` Stephen C. Tweedie
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=199902092257.WAA05676@dax.scot.redhat.com \
--to=sct@redhat.com \
--cc=blah@kvack.org \
--cc=daniel@msc.cornell.edu \
--cc=ebiederm+eric@ccr.net \
--cc=linux-mm@kvack.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