DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Tan, Jianfeng" <jianfeng.tan@intel.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>,
	Pankaj Chauhan <pankaj.chauhan@nxp.com>
Cc: dev@dpdk.org, hemant.agrawal@nxp.com, shreyansh.jain@nxp.com
Subject: Re: [dpdk-dev] vhost [query] : support for multiple ports and non VMDQ devices in vhost switch
Date: Wed, 17 Aug 2016 10:33:54 +0800	[thread overview]
Message-ID: <aa5c8eda-8f59-3855-5797-1b18209c2ae9@intel.com> (raw)
In-Reply-To: <20160816025614.GM30752@yliu-dev.sh.intel.com>

Hi,

Please review below proposal of Pankaj and myself after an offline 
discussion. (Pankaj, please correct me if I'm going somewhere wrong).

a. Remove HW dependent option, --strip-vlan, because different kinds of 
NICs behave differently. It's a bug fix.
b. Abstract switching logic into a framework, so that we can develop 
different kinds of switching logics. In this phase, we will have two 
switching logics: (1) a simple software-based mac learning switching; 
(2) VMDQ based switching. Any other advanced switching logics can be 
proposed based on this framework.
c. Merge tep_termination example vxlan as a switching logic of the 
framework.

To be decided:
d. Support multiple physical ports.
e. Keep the current way to use vhost lib directly or use vhost pmd instead.

On 8/16/2016 10:56 AM, Yuanhan Liu wrote:
> 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)?

Example testpmd will not allow those complex switching logics.

Thanks,
Jianfeng

> 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-17  2:33 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
2016-08-17  2:33     ` Tan, Jianfeng [this message]
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=aa5c8eda-8f59-3855-5797-1b18209c2ae9@intel.com \
    --to=jianfeng.tan@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=pankaj.chauhan@nxp.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=yuanhan.liu@linux.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).