Re: Frontswap [PATCH 0/4] (was Transcendent Memory): overview

[Avi Kivity]

On 04/23/2010 06:56 PM, Dan Magenheimer wrote:
> > > Each page is either in frontswap OR on the normal swap device,
> > > never both.  So, yes, both reads and writes are avoided if memory
> > > is available and there is no write issued to the io subsystem if
> > > memory is available.  The is_memory_available decision is determined
> > > by the hypervisor dynamically for each page when the guest attempts
> > > a "frontswap_put".  So, yes, you are indeed "swapping to the
> > > hypervisor" but, at least in the case of Xen, the hypervisor
> > > never swaps any memory to disk so there is never double swapping.
> > >        
> > I see.  So why not implement this as an ordinary swap device, with a
> > higher priority than the disk device?  this way we reuse an API and
> > keep
> > things asynchronous, instead of introducing a special purpose API.
> >      
> Because the swapping API doesn't adapt well to dynamic changes in
> the size and availability of the underlying "swap" device, which
> is very useful for swap to (bare-metal) hypervisor.
>    

Can we extend it?  Adding new APIs is easy, but harder to maintain in 
the long term.

> > Doesn't this commit the hypervisor to retain this memory?  If so, isn't
> > it simpler to give the page to the guest (so now it doesn't need to
> > swap at all)?
> >      
> Yes the hypervisor is committed to retain the memory.  In
> some ways, giving a page of memory to a guest (via ballooning)
> is simpler and in some ways not.  When a guest "owns" a page,
> it can do whatever it wants with it, independent of what is best
> for the "whole" virtualized system.  When the hypervisor
> "owns" the page on behalf of the guest but the guest can't
> directly address it, the hypervisor has more flexibility.
> For example, tmem optionally compresses all frontswap pages,
> effectively doubling the size of its available memory.
> In the future, knowing that a guest application can never
> access the pages directly, it might store all frontswap pages in
> (slower but still synchronous) phase change memory or "far NUMA"
> memory.
>    

Ok.  For non traditional RAM uses I really think an async API is 
needed.  If the API is backed by a cpu synchronous operation is fine, 
but once it isn't RAM, it can be all kinds of interesting things.

Note that even if you do give the page to the guest, you still control 
how it can access it, through the page tables.  So for example you can 
easily compress a guest's pages without telling it about it; whenever it 
touches them you decompress them on the fly.

> > I think it will be true in an overwhelming number of cases.  Flash is
> > new enough that most devices support scatter/gather.
> >      
> I wasn't referring to hardware capability but to the availability
> and timing constraints of the pages that need to be swapped.
>    

I have a feeling we're talking past each other here.  Swap has no timing 
constraints, it is asynchronous and usually to slow devices.


--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/