From: William Lee Irwin III <wli@holomorphy.com>
To: "David S. Miller" <davem@redhat.com>
Cc: pj@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Does io_remap_page_range() take 5 or 6 args?
Date: Wed, 18 Aug 2004 16:33:24 -0700 [thread overview]
Message-ID: <20040818233324.GT11200@holomorphy.com> (raw)
In-Reply-To: <20040818161658.49aa8de3.davem@redhat.com>
On Wed, 18 Aug 2004 15:59:15 -0700
>> Given this, will a pfn suffice?
On Wed, Aug 18, 2004 at 04:16:58PM -0700, David S. Miller wrote:
> There is an error in the calculations. 16TB "RAM", means "RAM".
> On many systems, a large chunk of the physical address space is
> taken up by I/O areas, not real memory.
> Such areas do not take up mem_map[] array space.
> Regardless, I think an "unsigned long" page frame number is sufficient
> for now. Don't even make the new type.
Oh, virtualspace footprint of IO areas is far worse, as the convention
is to direct map them into a single address space if they're ever used.
Of course this convention is much more loosely established than e.g.
struct page is for RAM. Some analogue of kmap_atomic() for such
machines to multiplex virtualspace in interrupt context would help, but
is unrelated to physical address passing issues.
-- wli
next prev parent reply other threads:[~2004-08-18 23:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 20:33 Does io_remap_page_range() take 5 or 6 args? Paul Jackson
2004-08-18 20:53 ` William Lee Irwin III
2004-08-18 20:55 ` David S. Miller
2004-08-18 20:56 ` David S. Miller
2004-08-18 21:05 ` William Lee Irwin III
2004-08-18 21:30 ` David S. Miller
2004-08-18 21:40 ` William Lee Irwin III
2004-08-18 22:00 ` William Lee Irwin III
2004-08-18 22:59 ` William Lee Irwin III
2004-08-18 23:16 ` David S. Miller
2004-08-18 23:33 ` William Lee Irwin III [this message]
2004-08-19 2:38 ` William Lee Irwin III
2004-08-19 2:43 ` David S. Miller
2004-08-19 2:51 ` William Lee Irwin III
2004-08-18 21:36 ` Richard B. Johnson
2004-08-18 20:54 ` David S. Miller
2004-08-18 21:15 ` Paul Jackson
2004-08-18 21:35 ` 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=20040818233324.GT11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.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.