From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: GongJinrong <jinronggong@hotmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] About a zero copy framework
Date: Tue, 10 Dec 2013 22:09:27 +0100 [thread overview]
Message-ID: <462237291.xmhSuQ6GWE@x220> (raw)
In-Reply-To: <COL131-DS22A1D0FFBAE5E726E34810B7D20@phx.gbl>
Hello,
10/12/2013 17:40, GongJinrong :
> I am trying to develop an open source guest/host zero copy
> communication channel framework for kvm, I found DPDK has similar module,
> but it seems couples with intel NICs, how can I use DPDK to do the zero copy
> for kvm without intel NICs(host to guest or guest to guest)? I only need a
> data channel framework.
Have you seen virtio-net-pmd ?
http://dpdk.org/browse/virtio-net-pmd
It could be close to what you want.
--
Thomas
next prev parent reply other threads:[~2013-12-10 21:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.0.1386667792.31234.dev@dpdk.org>
2013-12-10 9:40 ` GongJinrong
2013-12-10 21:09 ` Thomas Monjalon [this message]
2013-12-11 2:21 ` jinho hwang
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=462237291.xmhSuQ6GWE@x220 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=jinronggong@hotmail.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;
as well as URLs for NNTP newsgroup(s).