From: Tetsuya Mukawa <mukawa@igel.co.jp>
To: "O'driscoll, Tim" <tim.o'driscoll@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] DPDK Features for Q1 2015
Date: Thu, 23 Oct 2014 12:17:28 +0900 [thread overview]
Message-ID: <54487348.60805@igel.co.jp> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com>
Hi All,
(2014/10/22 22:48), O'driscoll, Tim wrote:
> Single Virtio Driver: Merge existing Virtio drivers into a single implementation, incorporating the best features from each of the existing drivers.
It's nice plan. We should do it.
In my understanding, the following drivers could be merged into a single
virtio PMD since they consist of similar code for handling the virtio ring.
- librte_pmd_virtio
- librte_pmd_xenvirt
- librte_vhost (cuse)
librte_vhost is not a PMD, but we can easily write a librte_pmd_vhost
based on librte_vhost.
Before doing it, we need to consider vhost-user extension for librte_vhost.
BTW, I have a RFC patch for librte_vhost to handle vhost-user.
It may be the first step to merge all virtio drivers.
My patch introduces an abstraction layer to hide differences between
legacy cuse vhost and vhost-user from DPDK apps.
Also in my patch, virtio negotiation and initialization code and virtio
handling code is separated.
So, legacy cuse vhost and vhost-user can share virtio handling code
Anyway, I will send a RFC patch soon as the first step of merging all
virtio drivers.
Thanks,
Tetsuya
next prev parent reply other threads:[~2014-10-23 3:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 13:48 O'driscoll, Tim
2014-10-22 14:20 ` [dpdk-dev] " Thomas Monjalon
2014-10-22 14:44 ` Zhou, Danny
2014-10-22 15:05 ` Liang, Cunming
2014-10-22 16:10 ` [dpdk-dev] [dpdk-announce] " Luke Gorrie
2014-10-23 12:29 ` O'driscoll, Tim
2014-10-22 19:22 ` Matthew Hall
2014-10-24 8:10 ` O'driscoll, Tim
2014-10-24 10:10 ` Thomas Monjalon
2014-10-24 19:02 ` Matthew Hall
2014-10-24 19:01 ` Matthew Hall
2014-10-23 3:06 ` Tetsuya Mukawa
2014-10-23 10:04 ` O'driscoll, Tim
2014-10-23 3:17 ` Tetsuya Mukawa [this message]
2014-10-23 11:27 ` O'driscoll, Tim
2014-10-31 22:05 ` Xie, Huawei
2014-11-02 12:50 ` Tetsuya Mukawa
2014-10-23 14:18 ` [dpdk-dev] Fwd: " Jay Rolette
2014-10-23 14:52 ` Alex Markuze
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=54487348.60805@igel.co.jp \
--to=mukawa@igel.co.jp \
--cc=dev@dpdk.org \
--cc=tim.o'driscoll@intel.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).