|
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: |
"Chris Friesen" <cfriesen@xxxxxxxxxx> |
|
Date: |
Mon, 22 Jun 2009 08:31:02 -0600 |
|
Cc: |
npiggin@xxxxxxx, akpm@xxxxxxxx, jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, tmem-devel@xxxxxxxxxxxxxx, alan@xxxxxxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, kurt.hackel@xxxxxxxxxx, 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>, Martin Schwidefsky <schwidefsky@xxxxxxxxxx>, chris.mason@xxxxxxxxxx, Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx> |
|
Delivery-date: |
Mon, 22 Jun 2009 07:52:09 -0700 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<cd40cd91-66e9-469d-b079-3a899a3ccadb@default> |
|
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: |
<cd40cd91-66e9-469d-b079-3a899a3ccadb@default> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Mozilla Thunderbird 1.0.2-6 (X11/20050513) |
Dan Magenheimer wrote:
> What if there was a class of memory that is of unknown
> and dynamically variable size, is addressable only indirectly
> by the kernel, can be configured either as persistent or
> as "ephemeral" (meaning it will be around for awhile, but
> might disappear without warning), and is still fast enough
> to be synchronously accessible?
>
> We call this latter class "transcendent memory"
While true that this memory is "exceeding usual limits", the more
important criteria is that it may disappear.
It might be clearer to just call it "ephemeral memory".
There is going to be some overhead due to the extra copying, and at
times there could be two copies of data in memory. It seems possible
that certain apps right a the borderline could end up running slower
because they can't fit in the regular+ephemeral memory due to the
duplication, while the same amount of memory used normally could have
been sufficient.
I suspect trying to optimize management of this could be difficult.
Chris
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
Home