From: Pankaj Chauhan <pankaj.chauhan@nxp.com>
To: <yuanhan.liu@linux.intel.com>, <dev@dpdk.org>
Cc: <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: Wed, 17 Aug 2016 15:54:21 +0530 [thread overview]
Message-ID: <279ceed3-4645-b8ae-9809-dd10b9fd66b4@nxp.com> (raw)
In-Reply-To: <20160816025614.GM30752@yliu-dev.sh.intel.com>
On 8/16/2016 8:26 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.
Yes I had a discussion with Jianfeng and he has sent the work items on
the list.
>
>> 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
My use case is that my machine/board which is not sitting as end node of
network but somewhere in between like an router. So the traffic looks
something like this:
Physical port 1 -> Enter VM(s) through virtio -> exit from physical port 2
For above use case i need a vhost-back-end which supports multiple
physical ports.
Thanks for the suggestion of vhost-pmd ( i was not aware of that), i'll
explore possibility of using it for my use case of multiple physical ports.
thanks,
Pankaj
>
next prev parent reply other threads:[~2016-08-17 10:24 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
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 [this message]
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=279ceed3-4645-b8ae-9809-dd10b9fd66b4@nxp.com \
--to=pankaj.chauhan@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jianfeng.tan@intel.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).