DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuanhan Liu <yuanhan.liu@linux.intel.com>
To: Pankaj Chauhan <pankaj.chauhan@nxp.com>
Cc: dev@dpdk.org, hemant.agrawal@nxp.com, shreyansh.jain@nxp.com,
	"Tan, Jianfeng" <jianfeng.tan@intel.com>
Subject: Re: [dpdk-dev] vhost [query] : support for multiple ports and non VMDQ devices in vhost switch
Date: Tue, 16 Aug 2016 10:56:14 +0800	[thread overview]
Message-ID: <20160816025614.GM30752@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <c94ee313-24f6-2a50-50a1-223375cf335a@nxp.com>

On Tue, Aug 09, 2016 at 04:42:33PM +0530, Pankaj Chauhan wrote:
> 
> Hi,
> 
> I am working on an NXP platform where we intend to use user space vhost
> switch (examples/vhost) as backend for VIRTIO devices. But there are two
> limitations in current vhost-switch (examples/vhost)that are restricting my
> use case:
> 
> 1. The vhost-switch application is tightly integrated with Intel VMDQ. Since
> my device doesn't have VMDQ i can not use this application directly.

Sorry being late (I was on biz trip last week).

Yes, a vhost example should not do that. We have an internal TODO to
remove it. Actually, to make it optional, and Jianfeng was working on
that. Well, seems that you two have already had some discussions.

> 2. The vhost-switch application supports only one external or physical port
> (non virtio devices), but my requirement is to have multiple physical ports
> and multiple virtio devices.

What are you going to achieve? BTW, have you tried testpmd (with vhost-pmd)?
I'm with impression that it might be a better option to you.

	--yliu

> In summary my requirement is to do whatever vhost-switch is doing, in
> addition to that add support for following:
> 
> 1. support devices that don't have VMDQ.
> 2. Support multiple physical ports.
> 
> I need suggestions on the approach i should take: whether to add support of
> above mentioned in existing vhost-switch (examples/vhost) or write another
> application (based on librte_vhost only) to support my requirements.
> 
> I'll work on it after the suggestion i get from the list, and send the RFC
> patch.
> 
> Thanks,
> Pankaj
> 

  reply	other threads:[~2016-08-16  2:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b25fa14e-1dae-da7d-a320-4ce53517ee85@nxp.com>
2016-08-09 11:12 ` Pankaj Chauhan
2016-08-16  2:56   ` Yuanhan Liu [this message]
2016-08-17  2:33     ` Tan, Jianfeng
2016-08-17 11:18       ` Maxime Coquelin
2016-08-18  2:35         ` Tan, Jianfeng
2016-08-18  7:43           ` Maxime Coquelin
2016-08-18 10:36             ` Tan, Jianfeng
2016-08-22 13:19               ` Thomas Monjalon
2016-08-24  7:28           ` Maxime Coquelin
2016-08-26  5:53             ` Pankaj Chauhan
2016-08-17 10:24     ` Pankaj Chauhan
2016-08-18  8:27       ` Yuanhan Liu

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=20160816025614.GM30752@yliu-dev.sh.intel.com \
    --to=yuanhan.liu@linux.intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jianfeng.tan@intel.com \
    --cc=pankaj.chauhan@nxp.com \
    --cc=shreyansh.jain@nxp.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).