From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 983AD5592 for ; Wed, 17 Aug 2016 04:33:57 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga102.fm.intel.com with ESMTP; 16 Aug 2016 19:33:56 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,529,1464678000"; d="scan'208";a="1042482082" Received: from shwdeisgchi083.ccr.corp.intel.com (HELO [10.239.67.193]) ([10.239.67.193]) by fmsmga002.fm.intel.com with ESMTP; 16 Aug 2016 19:33:55 -0700 To: Yuanhan Liu , Pankaj Chauhan References: <20160816025614.GM30752@yliu-dev.sh.intel.com> Cc: dev@dpdk.org, hemant.agrawal@nxp.com, shreyansh.jain@nxp.com From: "Tan, Jianfeng" Message-ID: Date: Wed, 17 Aug 2016 10:33:54 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160816025614.GM30752@yliu-dev.sh.intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] vhost [query] : support for multiple ports and non VMDQ devices in vhost switch X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2016 02:33:58 -0000 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 >>