From: William Lee Irwin III <wli@holomorphy.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: "'Hirokazu Takahashi'" <taka@valinux.co.jp>,
linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org, "Seth,
Rohit" <rohit.seth@intel.com>
Subject: Re: Hugetlb demanding paging for -mm tree
Date: Mon, 9 Aug 2004 12:12:49 -0700 [thread overview]
Message-ID: <20040809191249.GT11200@holomorphy.com> (raw)
In-Reply-To: <200408091819.i79IJ3Y12216@unix-os.sc.intel.com>
William Lee Irwin III wrote on Friday, August 06, 2004 2:08 PM
>> update_mmu_cache() does not appear to check the size of the translation
>> to be established in many architectures. e.g. on arch/ia64/ it does
>> flush_icache_range(addr, addr + PAGE_SIZE) unconditionally, and only
>> sets PG_arch_1 on a single struct page. Similar comments apply to
>> sparc64 and ppc64; I didn't check any others.
On Mon, Aug 09, 2004 at 11:19:04AM -0700, Chen, Kenneth W wrote:
> I suppose this is fixable in update_mmu_cache() where it can check the
> type of pte and do appropriate sizing and other things. ia64 would have
> to check the address instead of looking at the pte.
Yes, it's just a fair amount of document-hunting since there isn't
always easily cut-and-pasteable stuff (e.g. ITAG_MASK for larger page
sizes was omitted from the #ifdefs on sparc64).
As for ia64 checking addresses... ew, can't we just use long format
VHPT? The virtual placement constraints are nasty.
-- wli
next prev parent reply other threads:[~2004-08-09 19:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 13:29 Hugetlb demanding paging for -mm tree Chen, Kenneth W
2004-08-05 13:36 ` William Lee Irwin III
2004-08-05 13:39 ` Chen, Kenneth W
2004-08-05 16:35 ` Hirokazu Takahashi
2004-08-06 20:55 ` Chen, Kenneth W
2004-08-06 21:07 ` William Lee Irwin III
2004-08-07 8:13 ` William Lee Irwin III
2004-08-09 18:19 ` Chen, Kenneth W
2004-08-09 19:12 ` William Lee Irwin III [this message]
2004-08-07 8:36 ` William Lee Irwin III
2004-08-09 18:54 ` Chen, Kenneth W
2004-08-09 19:12 ` William Lee Irwin III
2004-08-05 13:42 ` Chen, Kenneth W
2004-08-05 14:04 ` Andi Kleen
2004-08-06 21:06 ` Chen, Kenneth W
2004-08-05 13:43 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-08-09 18:43 Seth, Rohit
2004-08-09 18:59 ` William Lee Irwin III
2004-08-10 8:52 Seth, Rohit
2004-08-10 8:55 ` William Lee Irwin III
2004-08-11 0:28 Seth, Rohit
2004-08-11 0:45 ` William Lee Irwin III
2004-08-11 6:36 Seth, Rohit
2004-08-11 6:38 ` William Lee Irwin III
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=20040809191249.GT11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rohit.seth@intel.com \
--cc=taka@valinux.co.jp \
/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