[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] RE: [RFC] transcendent memory for Linux
- To: Chris Friesen <cfriesen@xxxxxxxxxx>
- From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
- Date: Mon, 22 Jun 2009 13:50:36 -0700 (PDT)
- 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>, Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx>, chris.mason@xxxxxxxxxx, Rik
- Delivery-date: Wed, 24 Jun 2009 05:51:31 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
> > 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".
Ephemeral tmem (precache) may be the most interesting, but there
is persistent tmem (preswap) as well. Both are working today
and both are included in the patches I posted.
Looking for a term encompassing both, I chose "transcendent".
> 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.
This is likely true, but I expect the duplicates to be few
and transient and a very small fraction of the total memory cost for
virtualization (and similar abstraction technologies).
> I suspect trying to optimize management of this could be difficult.
True. Optimizing the management of ANY resource across many
consumers is difficult. But wasting the resource because its
a pain to optimize doesn't seem to be a good answer either.
Xen-devel mailing list