[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4EC29367.9040106@redhat.com>
Date: Tue, 15 Nov 2011 11:29:27 -0500
From: Rik van Riel <riel@...hat.com>
To: Dan Magenheimer <dan.magenheimer@...cle.com>
CC: Andrea Arcangeli <aarcange@...hat.com>,
Pekka Enberg <penberg@...nel.org>,
Cyclonus J <cyclonusj@...il.com>,
Sasha Levin <levinsasha928@...il.com>,
Christoph Hellwig <hch@...radead.org>,
David Rientjes <rientjes@...gle.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Konrad Wilk <konrad.wilk@...cle.com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Seth Jennings <sjenning@...ux.vnet.ibm.com>, ngupta@...are.org,
Chris Mason <chris.mason@...cle.com>, JBeulich@...ell.com,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Jonathan Corbet <corbet@....net>
Subject: Re: [GIT PULL] mm: frontswap (for 3.2 window)
On 11/02/2011 05:14 PM, Dan Magenheimer wrote:
> It occurs to me that batching could be done locally without
> changing the in-kernel "API" (i.e. frontswap_ops)... the
> guest-side KVM tmem-backend-driver could do the compression
> into guest-side memory and make a single
> hypercall=vmexit/vmenter whenever it has collected enough for
> a batch.
That seems like the best way to do it, indeed.
Do the current hooks allow that mode of operation,
or do the hooks only return after the entire operation
has completed?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists