From: Andrea Arcangeli <andrea@suse.de>
To: Christoph Rohland <cr@sap.com>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@transmeta.com>
Subject: Re: pte-highmem-5
Date: Thu, 17 Jan 2002 17:37:01 +0100 [thread overview]
Message-ID: <20020117173701.R4847@athlon.random> (raw)
In-Reply-To: <20020116185814.I22791@athlon.random> <m3u1tll6pb.fsf@linux.local> <20020117163021.L4847@athlon.random> <m3bsft7ygd.fsf@linux.local>
In-Reply-To: <m3bsft7ygd.fsf@linux.local>; from cr@sap.com on Thu, Jan 17, 2002 at 05:11:48PM +0100
On Thu, Jan 17, 2002 at 05:11:48PM +0100, Christoph Rohland wrote:
> Hi Andrea,
>
> On Thu, 17 Jan 2002, Andrea Arcangeli wrote:
> > (btw, I suspect allocating one page at offset 4G in every shmfs file
> > could make the overhead per page of shm to increase)
>
> Nearly: A sparse file with the only page at 4G is the worst case: You
> need three extra pages to hold the swap entry. The ratio goes fown as
> soon as you add more pages somewhere.
Agreed.
>
> > But in real life I really don't expect problems here, one left page
> > of the vector holds 1024 swap entries, so the overhead is of the
> > order of 1/1000. On the top of my head (without any precise
> > calculation) 64G of shm would generate stuff of the order of some
> > houndred mbytes of ram
>
> Ok, 64GB shm allocate roughly 64MB swap entries, so this case should
> not bother too much. I was still at the 390x case where we have 512
> entries per page. But they do not need highmem.
agreed.
> Another case are smaller machines with big tmpfs instances: They get
> killed by the swap entries. But you cannot hinder that without
> swapping the swap entries themselves.
yes, same can happen with pagetables, if you've an huge amount of swap
and only a few mbytes of ram, that's another kind of problem that we
always ignored so far (mostly because it is possible to solve it very
efficiently by throwing money into some more ram :).
Andrea
next prev parent reply other threads:[~2002-01-17 16:36 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 17:58 pte-highmem-5 Andrea Arcangeli
2002-01-16 18:04 ` pte-highmem-5 Linus Torvalds
2002-01-16 18:35 ` pte-highmem-5 Andrea Arcangeli
2002-01-16 18:19 ` pte-highmem-5 Linus Torvalds
2002-01-16 18:48 ` pte-highmem-5 Andrea Arcangeli
2002-01-16 19:11 ` pte-highmem-5 Linus Torvalds
2002-01-16 19:30 ` pte-highmem-5 Andrea Arcangeli
2002-01-16 19:30 ` pte-highmem-5 Benjamin LaHaise
2002-01-16 19:50 ` pte-highmem-5 Andrea Arcangeli
2002-01-16 19:34 ` pte-highmem-5 Rik van Riel
2002-01-17 8:31 ` pte-highmem-5 Christoph Rohland
2002-01-17 12:14 ` pte-highmem-5 Hugh Dickins
2002-01-17 15:45 ` pte-highmem-5 Andrea Arcangeli
2002-01-17 16:08 ` pte-highmem-5 Hugh Dickins
2002-01-17 15:30 ` pte-highmem-5 Andrea Arcangeli
2002-01-17 16:11 ` pte-highmem-5 Christoph Rohland
2002-01-17 16:37 ` Andrea Arcangeli [this message]
2002-01-17 17:31 ` pte-highmem-5 Rik van Riel
2002-01-17 17:57 ` pte-highmem-5 Hugh Dickins
2002-01-17 18:09 ` pte-highmem-5 Andrea Arcangeli
2002-01-17 19:02 ` pte-highmem-5 Hugh Dickins
2002-01-18 2:38 ` pte-highmem-5 Andrea Arcangeli
2002-01-19 20:56 ` pte-highmem-5 Hugh Dickins
2002-01-21 18:15 ` pte-highmem-5 Andrea Arcangeli
2002-01-22 18:01 ` pte-highmem-5 Hugh Dickins
2002-01-22 19:10 ` pte-highmem-5 Andrea Arcangeli
2002-01-22 21:41 ` pte-highmem-5 Hugh Dickins
2002-01-22 23:34 ` pte-highmem-5 Andrea Arcangeli
2002-01-23 0:56 ` pte-highmem-5 Paul Mackerras
2002-01-23 1:27 ` pte-highmem-5 Andrea Arcangeli
2002-01-23 5:38 ` pte-highmem-5 Hugh Dickins
2002-01-23 16:29 ` pte-highmem-5 Daniel Phillips
2002-01-23 20:23 ` pte-highmem-5 Hugh Dickins
2002-01-24 3:09 ` pte-highmem-5 Andrea Arcangeli
2002-01-24 15:35 ` pte-highmem-5 Hugh Dickins
2002-01-22 19:29 ` pre4aa1 contig kmaps patch Hugh Dickins
2002-01-23 13:31 ` rwhron
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=20020117173701.R4847@athlon.random \
--to=andrea@suse.de \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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