From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>,
Pankaj Chauhan <pankaj.chauhan@nxp.com>
Cc: dev@dpdk.org, "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] vhost [query] : support for multiple ports and non VMDQ devices in vhost switch
Date: Mon, 22 Aug 2016 15:19:46 +0200 [thread overview]
Message-ID: <3244041.fTOXoYaKxg@xps13> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E3610639837@SHSMSX103.ccr.corp.intel.com>
2016-08-18 10:36, Tan, Jianfeng:
> From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com]
> > > On 8/17/2016 7:18 PM, Maxime Coquelin wrote:
> > >> On 08/17/2016 04:33 AM, Tan, Jianfeng wrote:
> > >>> 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.
[...]
> > >> Also, if we use pmd directly, then it would no more be a vhost switch
> > >> only, as it could potentially be used with physical NICs also.
> > >
> > > You mean we are building a switch instead of vhost switch? Yes, a switch
> > > can switch packets between virtio-virtio and virtio-physical nic.
> >
> > And physical-physical also, as we will be standard API with the
> > vhost-pmd, nothing will prevent using it with only physical switches,
> > no?
>
> Oh yes, I agree.
It looks to be a nice project.
I think you should start a new git repository in DPDK apps:
http://dpdk.org/browse/
And we could remove tep_termination and vhost examples.
next prev parent reply other threads:[~2016-08-22 13:19 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 [this message]
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=3244041.fTOXoYaKxg@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jianfeng.tan@intel.com \
--cc=maxime.coquelin@redhat.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).