linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Linux-MM <linux-mm@kvack.org>,
	Christoph Lameter <clameter@engr.sgi.com>,
	heiko.carstens@de.ibm.com
Subject: Re: [RFC][PATCH] vmemmap on sparsemem v2
Date: Sun, 10 Dec 2006 13:37:10 +0000	[thread overview]
Message-ID: <457C0D86.70603@shadowen.org> (raw)
In-Reply-To: <20061205214517.5ad924f6.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki wrote:
> Hi, this is patches for the virtual mem_map on sparsemem.
> 
> The virtual mem_map will reduce costs of page_to_pfn/pfn_to_page of
> SPARSEMEM_EXTREME.
> 
> I post this series in October but haven't been able to update.
> I rewrote the whole patches and reflected comments from Christoph-san and Andy-san.
> tested on ia64/tiger4.
> 
> Changes v1 -> v2:
> - support memory hotplug case.
> - uses static address for vmem_map (ia64)
> - added optimized pfn_valid() for ia64  (experimental)
> 
> consists of 5 patches:
> 1.. generic vmemmap_sparsemem
> 2.. memory hotplug support
> 3.. ia64 vmemmap_sparsemem definitions
> 4.. optimized pfn_valid  (experimental) 
> 5.. changes for pfn_valid  (experimental)
> 
> I don't manage large-page-size vmem_map in this series to keep patches simple.
> maybe I need more study to implement it in clean way.
> 
> This patch is against 2.6.19-rc6-mm2, and I'll rebase this to the next -mm
> (possibly). So this patch is just for RFC.
> 
> Any comments are welcome.
> -Kame

Sorry, I started reviewing v2 and out comes v3 :).

I have to say that I have generally been a virtual memap sceptic.  It 
seems complex and any testing I have done or seen doesn't seem to show 
any noticible performance benefit.

That said I do like the general thrust of this patch set.  There is 
basically no architecture specific component for this implementation 
other than specifying the base address.  This seems worth of testing 
(and I see akpm has already slurped this up) good.

Would we expect to see this replace the existing ia64 implementation in 
the long term?  I'd hate to see us having competing implementations 
here.  Also Heiko would this framework with your s390 requirements for 
vmem_map, I know that you have a particularly challenging physical 
layout?  It would be great to see just one of these in the kernel.

-apw

--
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>

  parent reply	other threads:[~2006-12-10 13:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-05 12:45 KAMEZAWA Hiroyuki
2006-12-05 12:49 ` [RFC][PATCH] vmemmap on sparsemem v2 [1/5] generic vmemmap on sparsemem KAMEZAWA Hiroyuki
2006-12-06 18:13   ` Heiko Carstens
2006-12-06 18:17     ` Christoph Lameter
2006-12-07  0:20       ` KAMEZAWA Hiroyuki
2006-12-07  0:20         ` Christoph Lameter
2006-12-07 10:11         ` Heiko Carstens
2006-12-07 10:50           ` KAMEZAWA Hiroyuki
2006-12-07 10:06       ` Heiko Carstens
2006-12-07 10:17         ` KAMEZAWA Hiroyuki
2006-12-08  3:06   ` KAMEZAWA Hiroyuki
2006-12-05 12:53 ` [RFC][PATCH] vmemmap on sparsemem v2 [2/5] memory hotplug support KAMEZAWA Hiroyuki
2006-12-05 12:59 ` [RFC][PATCH] vmemmap on sparsemem v2 [3/5] ia64 vmemamp on sparsemem KAMEZAWA Hiroyuki
2006-12-08  1:09   ` KAMEZAWA Hiroyuki
2006-12-05 13:09 ` [RFC][PATCH] vmemmap on sparsemem v2 [4/5] optimized pfn_valid KAMEZAWA Hiroyuki
2006-12-05 13:10 ` [RFC][PATCH] vmemmap on sparsemem v2 [5/5] optimzied pfn_valid support for ia64 KAMEZAWA Hiroyuki
2006-12-10 13:37 ` Andy Whitcroft [this message]
2006-12-10 15:19   ` [RFC][PATCH] vmemmap on sparsemem v2 Heiko Carstens
2006-12-11  1:09     ` KAMEZAWA Hiroyuki
2006-12-11 17:23     ` Christoph Lameter

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=457C0D86.70603@shadowen.org \
    --to=apw@shadowen.org \
    --cc=clameter@engr.sgi.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.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