linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <fletch@aracnet.com>
Cc: linux-mm@kvack.org
Subject: Re: [RFC] reduce usage of mem_map
Date: Fri, 2 Aug 2002 00:09:40 -0700	[thread overview]
Message-ID: <20020802070940.GA29537@holomorphy.com> (raw)
In-Reply-To: <869105998.1028245087@[10.10.2.3]>

jn Thu, Aug 01, 2002 at 11:38:07PM -0700, Martin J. Bligh wrote:
> I've tried to cut down the usage of mem_map somewhat.
> There's already macros to do the conversion between
> pfns to pages, and it doesn't work the way they've
> embedded it for discontigmem systems. Comments?
> Please don't apply - not tested yet ;-)
> M.

mem_map should be eliminated anyway. The concept is a legacy interface
for indexing into the older contiguous core map. The only pseudo-useful
thing it does is creating some kind of base address for address
calculation in page_to_pfn() etc., not that they're any kind of
performance-critical bit of the kernel. Those kinds of things can
circumvent the core VM without any significant ugliness impact.
Worse comes to worse, just do Roman Zippel's thing and shove the
page_address() bits into arch code where they'd belong if arches weren't
forcing us to keep ->virtual all the time (necessitating core control).

In the meantime, the necessity of laying out the pageframe maps in such
a manner that indexing from mem_map is sort of valid is an irritating
constraint not satisfiable without virtual remapping tricks and/or
MAP_NR_DENSE() on many platforms. Kill it. Kill it dead.


Cheers,
Bill
--
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/

      reply	other threads:[~2002-08-02  7:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-02  6:38 Martin J. Bligh
2002-08-02  7:09 ` William Lee Irwin III [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=20020802070940.GA29537@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=fletch@aracnet.com \
    --cc=linux-mm@kvack.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