From: Avi Kivity <avi@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Akshay Karle <akshay.a.karle@gmail.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
ashu tripathi <er.ashutripathi@gmail.com>,
nishant gulhane <nishant.s.gulhane@gmail.com>,
amarmore2006 <amarmore2006@gmail.com>,
Shreyas Mahure <shreyas.mahure@gmail.com>,
mahesh mohan <mahesh6490@gmail.com>
Subject: Re: [RFC 0/2] kvm: Transcendent Memory (tmem) on KVM
Date: Thu, 15 Mar 2012 20:10:57 +0200 [thread overview]
Message-ID: <4F6230B1.4010004@redhat.com> (raw)
In-Reply-To: <20120315180233.GF452@phenom.dumpdata.com>
On 03/15/2012 08:02 PM, Konrad Rzeszutek Wilk wrote:
> >
> > Nice. This takes care of the tail-end of the streaming (the more
> > important one - since it always involves a cold copy). What about the
> > other side? Won't the read code invoke cleancache_get_page() for every
> > page? (this one is just a null hypercall, so it's cheaper, but still
> > expensive).
>
> That is something we should fix - I think it was mentioned in the frontswap
> email thread the need for batching and it certainly seems required as those
> hypercalls aren't that cheap.
In fact when tmem was first proposed I asked for two changes - make it
batchable, and make it asynchronous (so we can offload copies to a dma
engine, etc). Of course that would have made tmem significantly more
complicated.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-03-15 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 16:29 [RFC 0/2] kvm: Transcendent Memory (tmem) on KVM Akshay Karle
2012-03-15 16:42 ` Konrad Rzeszutek Wilk
2012-03-15 16:48 ` Konrad Rzeszutek Wilk
2012-03-15 16:58 ` Avi Kivity
2012-03-15 17:49 ` Dan Magenheimer
2012-03-15 18:01 ` Avi Kivity
2012-03-15 18:02 ` Konrad Rzeszutek Wilk
2012-03-15 18:10 ` Avi Kivity [this message]
2012-03-15 19:36 ` Dan Magenheimer
2012-03-15 19:46 ` Konrad Rzeszutek Wilk
2012-03-15 19:16 ` Dan Magenheimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F6230B1.4010004@redhat.com \
--to=avi@redhat.com \
--cc=akshay.a.karle@gmail.com \
--cc=amarmore2006@gmail.com \
--cc=dan.magenheimer@oracle.com \
--cc=er.ashutripathi@gmail.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh6490@gmail.com \
--cc=nishant.s.gulhane@gmail.com \
--cc=shreyas.mahure@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox