From: "Seth, Rohit" <rohit.seth@intel.com>
To: "'David S. Miller'" <davem@redhat.com>, akpm@zip.com.au
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, "Seth,
Rohit" <rohit.seth@intel.com>,
"Saxena, Sunil" <sunil.saxena@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>
Subject: RE: large page patch
Date: Thu, 1 Aug 2002 18:34:04 -0700 [thread overview]
Message-ID: <25282B06EFB8D31198BF00508B66D4FA03EA56B3@fmsmsx114.fm.intel.com> (raw)
There is typo in Andrew's mail. It is not 256K, but it is 256MB.
-----Original Message-----
From: David S. Miller [mailto:davem@redhat.com]
Sent: Thursday, August 01, 2002 6:20 PM
To: akpm@zip.com.au
Cc: linux-kernel@vger.kernel.org; linux-mm@kvack.org;
rohit.seth@intel.com; sunil.saxena@intel.com; asit.k.mallick@intel.com
Subject: Re: large page patch
From: Andrew Morton <akpm@zip.com.au>
Date: Thu, 01 Aug 2002 18:26:40 -0700
"David S. Miller" wrote:
> This is probably done to increase the likelyhood that 4MB page orders
> are available. If we collapse 4MB pages deeper, they are less likely
> to be broken up because smaller orders would be selected first.
This is leakage from ia64, which supports up to 256k pages.
Ummm, 4MB > 256K and even with a 4K PAGE_SIZE MAX_ORDER coalesces
up to 4MB already :-)
Apparently a page-table based representation could not be used by PPC.
The page-table is just an abstraction, there is no reason dummy
"large" ptes could not be used which are just ignored by the HW TLB
reload code.
--
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-mm.org/
next reply other threads:[~2002-08-02 1:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 1:34 Seth, Rohit [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-02 19:31 Seth, Rohit
2002-08-02 0:37 Andrew Morton
2002-08-02 0:43 ` David S. Miller
2002-08-02 1:26 ` Andrew Morton
2002-08-02 1:19 ` David S. Miller
2002-08-02 1:55 ` Rik van Riel
2002-08-02 1:50 ` David S. Miller
2002-08-02 2:29 ` Gerrit Huizenga
2002-08-02 2:23 ` David S. Miller
2002-08-02 2:53 ` Gerrit Huizenga
2002-08-02 5:24 ` David Mosberger
2002-08-02 5:20 ` David S. Miller
2002-08-02 6:26 ` David Mosberger
2002-08-02 6:33 ` Martin J. Bligh
2002-08-02 6:44 ` David Mosberger
2002-08-02 10:00 ` Marcin Dalecki
2002-08-02 7:08 ` Andrew Morton
2002-08-02 7:15 ` William Lee Irwin III
2002-08-02 8:20 ` David S. Miller
2002-08-02 9:05 ` Ryan Cumming
2002-08-02 9:06 ` David S. Miller
2002-08-02 12:52 ` Rik van Riel
2002-08-02 15:27 ` David Mosberger
2002-08-02 1:09 ` Martin J. Bligh
2002-08-02 1:36 ` Andrew Morton
2002-08-02 4:31 ` Daniel Phillips
2002-08-02 4:47 ` Andrew Morton
2002-08-02 3:47 ` William Lee Irwin III
2002-08-02 23:40 ` Chris Wedgwood
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=25282B06EFB8D31198BF00508B66D4FA03EA56B3@fmsmsx114.fm.intel.com \
--to=rohit.seth@intel.com \
--cc=akpm@zip.com.au \
--cc=asit.k.mallick@intel.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sunil.saxena@intel.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