From: Vincent JARDIN <vincent.jardin@6wind.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] dev@DPDK Hackathon Proposal
Date: Tue, 19 May 2015 07:22:32 -0700 [thread overview]
Message-ID: <555B4728.5070409@6wind.com> (raw)
In-Reply-To: <0C5AFCA4B3408848ADF2A3073F7D8CC86D60323A@IRSMSX109.ger.corp.intel.com>
On 19/05/2015 07:18, Butler, Siobhan A wrote:
>> Also related to this, I would hope to participate in any discussion about OVS
>> >acceration and vhost/guest access acceleration.
We need to have this track with both:
- Qemu/kvm/libvirt session during the LinuxCon,
- virtio session during the LinuxConf
next prev parent reply other threads:[~2015-05-19 14:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 18:18 Butler, Siobhan A
2015-05-19 12:59 ` O'Driscoll, Tim
2015-05-19 13:36 ` Thomas F Herbert
2015-05-19 13:43 ` Rao, Ravi
2015-05-19 14:09 ` Thomas F Herbert
2015-05-19 14:18 ` Butler, Siobhan A
2015-05-19 14:22 ` Vincent JARDIN [this message]
2015-05-19 14:46 ` Thomas F Herbert
2015-05-19 16:08 ` Czesnowicz, Przemyslaw
2015-05-19 17:06 ` Rao, Ravi
2015-05-19 21:22 ` Traynor, Kevin
2015-05-19 18:18 ` Rao, Ravi
2015-05-19 14:20 ` Vincent JARDIN
2015-05-19 14:23 ` Butler, Siobhan 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=555B4728.5070409@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=dev@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).