WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [RFC] transcendent memory for Linux

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Subject: [Xen-devel] Re: [RFC] transcendent memory for Linux
From: Roland Dreier <rdreier@xxxxxxxxx>
Date: Tue, 30 Jun 2009 20:41:01 -0700
Authentication-results: sj-dkim-1; header.From=rdreier@xxxxxxxxx; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: npiggin@xxxxxxx, akpm@xxxxxxxx, jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, tmem-devel@xxxxxxxxxxxxxx, alan@xxxxxxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, Linus Walleij <linus.ml.walleij@xxxxxxxxx>, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, dave.mccracken@xxxxxxxxxx, Marcelo Tosatti <mtosatti@xxxxxxxxxx>, Himanshu Raj <rhim@xxxxxxxxxxxxx>, sunil.mushran@xxxxxxxxxx, Avi Kivity <avi@xxxxxxxxxx>, kurt.hackel@xxxxxxxxxx, Martin Schwidefsky <schwidefsky@xxxxxxxxxx>, linux-embedded@xxxxxxxxxxxxxxx, chris.mason@xxxxxxxxxx, Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 06 Jul 2009 08:04:42 -0700
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=413; t=1246419662; x=1247283662; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=rdreier@xxxxxxxxx; z=From:=20Roland=20Dreier=20<rdreier@xxxxxxxxx> |Subject:=20Re=3A=20[RFC]=20transcendent=20memory=20for=20L inux |Sender:=20; bh=Q9Dk/MpK4q5xNOlEm01dZQuWnmDIeLZkAa1oem7Gw1w=; b=k69C2HQRhr4epK+IzVJ+v6rJB0gpdQHLYbLF+1yYIRMTx/9CIzS955tI0v j1NpSMbQaQgbOyzUIGfxFiqGje5FUimjgx+SRGjobdUtDDJloQvyvPOi+7HN Rz/q7p6UmE6PfCUxOY47yhfgW6Cb9LJrOhHzXkj4WCw4Cuc6Zx66U=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5331ec14-c599-4317-bd5b-55911b8ee916@default> (Dan Magenheimer's message of "Mon, 29 Jun 2009 07:44:50 -0700 (PDT)")
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <5331ec14-c599-4317-bd5b-55911b8ee916@default>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.91 (gnu/linux)
 > One issue though: I would guess that copying pages of memory
 > could be very slow in an inexpensive embedded processor.

And copying memory could very easily burn enough power by keeping the
CPU busy that you lose the incremental gain of turning the memory off
vs. just going to self refresh.  (And the copying latency would easily
be as bad as the transition latency to/from self-refresh).

 - R.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>