linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: sparsemem & sparsemem extreme question
Date: Wed, 5 Oct 2005 17:58:23 +0200	[thread overview]
Message-ID: <20051005155823.GA10119@osiris.ibm.com> (raw)
In-Reply-To: <1128527554.26009.2.camel@localhost>

> > > to be traversed during a lookup: the page tables.  Granted, the TLB will
> > > provide some caching, but a lookup on ia64 can potentially be much more
> > > expensive than the two cacheline misses that sparsemem extreme might
> > > have.
> > Sure, just that on s390 we have a 1:1 mapping anyway. So these lookups would
> > be more or less for free for us (compared to what we have now).
> Is the 1:1 mapping done with pagetables?  If so, it is not free.

Sure, it's done with pagetables. What I meant: we have the 1:1 mapping already
today. So adding anything to the vmalloc area won't make it more expensive.

> > Actually my concern is that whenever the address space that is covered with
> > SPARSEMEM_EXTREME is not sufficient just another layer of indirection needs
> > to be added.
> Do you have any performance numbers to back up your concerns, or is it
> more about the code complexity?

No, my concern is actually that the s390 archticture actually will come up
with some sort of memory that's present in the physical address space where
the most significant bit of the addresses will be turned _on_. That means we
would need to support the whole 64 bit physical address space...
Considering this, this would be good for at least one if not two additional
indirection layers, which would make the code too complex, IMHO.
That's why I think the vmem_map approach would be easiest to implement this :)

Heiko

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2005-10-05 15:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-04  6:50 Heiko Carstens
2005-10-04 14:33 ` Andy Whitcroft
2005-10-04 16:15 ` Dave Hansen
2005-10-05  6:39   ` Heiko Carstens
2005-10-05 15:52     ` Dave Hansen
2005-10-05 15:58       ` Heiko Carstens [this message]
2005-10-05 16:05         ` Dave Hansen
2005-10-05 16:10           ` Heiko Carstens
2005-10-05 16:20             ` Dave Hansen
2005-10-05 17:12               ` Heiko Carstens
2005-10-05 17:20                 ` Dave Hansen
2005-10-05 17:45                   ` Heiko Carstens
2005-10-05 17:57                     ` Dave Hansen
2005-10-05 18:04                       ` Heiko Carstens
2005-10-05 18:42                         ` Bob Picco
2005-10-05 22:06                         ` Dave Hansen
2005-10-06  7:39                           ` Heiko Carstens

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=20051005155823.GA10119@osiris.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=haveblue@us.ibm.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