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>,
"Wang, Zhihong" <zhihong.wang@intel.com>
Subject: Re: [dpdk-dev] vhost [query] : support for multiple ports and non VMDQ devices in vhost switch
Date: Thu, 18 Aug 2016 16:27:03 +0800 [thread overview]
Message-ID: <20160818082703.GV30752@yliu-dev.sh.intel.com> (raw)
In-Reply-To: <279ceed3-4645-b8ae-9809-dd10b9fd66b4@nxp.com>
On Wed, Aug 17, 2016 at 03:54:21PM +0530, Pankaj Chauhan wrote:
> 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
I'm not quite sure testpmd has this kind of support or not, routing the
data from a specific port to another specific port. Zhihong might have
the answer.
--yliu
> 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.
prev parent reply other threads:[~2016-08-18 8:18 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
2016-08-18 8:27 ` Yuanhan Liu [this message]
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=20160818082703.GV30752@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 \
--cc=zhihong.wang@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).