From: Gregory Haskins <gregory.haskins@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: alacrityvm-devel@lists.sourceforge.net,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
netdev@vger.kernel.org
Subject: Re: AlacrityVM benchmark numbers updated
Date: Wed, 26 Aug 2009 16:05:57 -0400 [thread overview]
Message-ID: <4A9595A5.9060809@gmail.com> (raw)
In-Reply-To: <4A958BA0.2000801@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 688 bytes --]
Avi Kivity wrote:
> On 08/26/2009 09:42 PM, Gregory Haskins wrote:
>> Actually, I have already look at this and it does indeed seem better to
>> use switch_mm+gupf() over gup() by quite a large margin. You could then
>> couple that with your DMA-engine idea to potentially gain even more
>> benefits (though probably not for networking since most NICs have their
>> own DMA engine anyway).
>>
>>
>
> For tx, we'll just go copyless once we plumb the destructors properly.
> But for rx on a shared interface it is impossible to avoid the copy.
> You can only choose if you want it done by the cpu or a local dma engine.
>
>
Yep, agree on both counts.
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
prev parent reply other threads:[~2009-08-26 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 1:01 AlacrityVM benchmark numbers updated Gregory Haskins
2009-08-26 10:16 ` Avi Kivity
2009-08-26 18:42 ` Gregory Haskins
2009-08-26 19:23 ` Avi Kivity
2009-08-26 20:05 ` Gregory Haskins [this message]
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=4A9595A5.9060809@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=alacrityvm-devel@lists.sourceforge.net \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).