From: "Avi Cohen (A)" <avi.cohen@huawei.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] VHOST-USER interface between ovs-dpdk and a VM
Date: Tue, 23 May 2017 13:27:14 +0000 [thread overview]
Message-ID: <B84047ECBD981D4B93EAE5A6245AA361013BCAE6@FRAEML521-MBX.china.huawei.com> (raw)
Hi,
I'm trying to understand the packet life-cycle in ovs-dpdk (running on host) communicating with a VM through vhost-user interface:
1. packet is received via physical port to the device.
2.DMA transfer to mempools on huge-pages allocated by dpdk-ovs - in user-space.
3. ovs-dpdk copies this packet to the shared-vring of the associated guest (shared between ovs-dpdk userspace process and guest)
4. no more copies in the guest - i.e. when any application running on the guest wants to consume the packet - there is a zero copy between the shared-vring and the guest application.
Is that correct ? how 4 is implemented ? this is a communication between OS in guest and application in guest . so how this is implemented with zero copy ?
Best Regards
avi
next reply other threads:[~2017-05-23 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 13:27 Avi Cohen (A) [this message]
2017-05-23 15:16 Avi Cohen (A)
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=B84047ECBD981D4B93EAE5A6245AA361013BCAE6@FRAEML521-MBX.china.huawei.com \
--to=avi.cohen@huawei.com \
--cc=users@dpdk.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).