From: Rik van Riel <riel@conectiva.com.br>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "David S. Miller" <davem@redhat.com>,
linux-mm@kvack.org, "Stephen C. Tweedie" <sct@redhat.com>,
Matthew Dillon <dillon@apollo.backplane.com>
Subject: Re: [RFC] 2-pointer PTE chaining idea
Date: Sat, 20 Jan 2001 17:58:48 +1100 (EST) [thread overview]
Message-ID: <Pine.LNX.4.31.0101201754110.1071-100000@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.10.10101182307340.9418-100000@penguin.transmeta.com>
On Thu, 18 Jan 2001, Linus Torvalds wrote:
> The only sane way I can think of to do the "implied pointer" is
> to do an order-2 allocation when you allocate a page directory:
While this idea seemed the best one at first glance, after
thinking about it a bit more I think your idea may actually
have _higher_ overhead than my idea of keeping the pte chain
structures external.
The reason for this is three-fold. Firstly, a lot of the page
tables will only be "occupied" for a small percentage. I don't
know the numbers, but I wouldn't be surprised if the page table
"occupation" is well under 50% for programs that are fully
resident ... probably less for programs which are partly swapped
out.
Secondly, if we do "dynamic" pte chaining, we can free up or
re-use the pte_chain structure as soon as we unmap a page, so
swapping out a page will free up the pte chain structure, which
is a big improvement compared to the unswappable page tables.
Thirdly, this idea doesn't suffer from memory fragmentation and
also works efficiently on architectures where the page table size
isn't equal to the page size.
Ideas ?
(btw, if I'm unlucky I won't be online again until the 26th)
regards,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com.br/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2001-01-20 6:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-19 5:08 Rik van Riel
2001-01-19 6:57 ` David S. Miller
2001-01-19 7:17 ` Linus Torvalds
2001-01-19 7:55 ` Rik van Riel
2001-01-20 5:22 ` Linus Torvalds
2001-01-20 5:31 ` David S. Miller
2001-01-20 7:05 ` Rik van Riel
2001-01-19 11:49 ` Ingo Molnar
2001-01-20 6:58 ` Rik van Riel [this message]
2001-01-19 11:37 ` Ingo Molnar
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=Pine.LNX.4.31.0101201754110.1071-100000@localhost.localdomain \
--to=riel@conectiva.com.br \
--cc=davem@redhat.com \
--cc=dillon@apollo.backplane.com \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
--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