From: "唐 宇" <ytang5@hotmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] about linux/ia64 mm
Date: Mon, 03 Dec 2001 10:01:05 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590698805579@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805562@msgid-missing>
ok, i found my answer;
for region 7,bit rr.ve is 0, so the VHPT walker is disabled for these two
regions; fault handler alt_[d/i]tlb_miss implement region-specific
translation algorithms(more simple and effecient) for it;
thx again;
>From: David Mosberger <davidm@hpl.hp.com>
>Reply-To: davidm@hpl.hp.com
>To: "唐 宇" <ytang5@hotmail.com>
>CC: linux-ia64@linuxia64.org
>Subject: Re: [Linux-ia64] about linux/ia64 mm
>Date: Thu, 29 Nov 2001 21:43:18 -0800
>
> >>>>> On Thu, 29 Nov 2001 23:19:53 +0800, "=?gb2312?B?zMYg0+4=?="
<ytang5@hotmail.com> said:
>
> Tang> hi all, i was a little confused by linux/ia64 mm; as i know,
> Tang> linux requires physical memory to be mapped contiguously to
> Tang> kernel space( don't care highmem); and PAGE_OFFSET is defined
> Tang> to 0xe000000000000000 in linux/ia64; that's region 7, its page
> Tang> size is fixed to 64M(2.4.12). how could __get_free_pages()
> Tang> allocate such a big _page_? it's absolutely impossible. so i
> Tang> think i made a big mistake somewhere, would someone help me
> Tang> out? thx :-)
>
>The page allocator works at the page frame level, which can be
>configured to have a size of 4, 8, 16, or 64KB. The large TLB
>mappings are used merely to access the underlying memory (think of it
>as a physical address space with a non-zero starting address).
>
> --david
_________________________________________________________________
您可以在 MSN Hotmail 站点 http://www.hotmail.com/cn 免费收发电子邮件
prev parent reply other threads:[~2001-12-03 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 15:19 [Linux-ia64] about linux/ia64 mm 唐 宇
2001-11-30 5:43 ` David Mosberger
2001-11-30 6:31 ` 唐 宇
2001-12-03 10:01 ` 唐 宇 [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=marc-linux-ia64-105590698805579@msgid-missing \
--to=ytang5@hotmail.com \
--cc=linux-ia64@vger.kernel.org \
/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