From: "Stephen C. Tweedie" <sct@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Jamie Lokier <lk@tantalophile.demon.co.uk>,
Ben LaHaise <bcrl@redhat.com>,
linux-mm@kvack.org
Subject: Re: [PATCH/RFC] fix missing tlb flush on x86 smp+pae
Date: Fri, 16 Mar 2001 17:29:31 +0000 [thread overview]
Message-ID: <20010316172931.V30889@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.31.0103160906490.17122-100000@penguin.transmeta.com>; from torvalds@transmeta.com on Fri, Mar 16, 2001 at 09:10:49AM -0800
Hi,
On Fri, Mar 16, 2001 at 09:10:49AM -0800, Linus Torvalds wrote:
>
> > On Intel, yes. The PAE case is a special case: we lose one bit of
> > addressing for each level of page table because the pte width has
> > doubled, so the two-level page table is short of two bits of address
> > coverage in PAE mode.
>
> I would almost tend to suggest that we just always allocate the PAE. Do it
> at the same time we allocate the page directory - make PAE use
> "get_pgd_slow()", and just always allocate the 3 pages. Much simpler.
It would probably be worth it: the binary, libraries and stack are
going to populate all 3 pages almost immediately anyway. I just hate
tweaking code just after we've finally got it stable. :)
--Stephen
--
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/
prev parent reply other threads:[~2001-03-16 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 19:50 [PATCH/RFC] fix missing tlb flush on x86 smp+pae Ben LaHaise
2001-03-16 13:12 ` Jamie Lokier
2001-03-16 13:34 ` Stephen C. Tweedie
2001-03-16 17:10 ` Linus Torvalds
2001-03-16 17:29 ` Stephen C. Tweedie [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=20010316172931.V30889@redhat.com \
--to=sct@redhat.com \
--cc=bcrl@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lk@tantalophile.demon.co.uk \
--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 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.