From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 410FC2C2F for ; Wed, 17 May 2017 14:50:44 +0200 (CEST) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga105.jf.intel.com with ESMTP; 17 May 2017 05:50:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,354,1491289200"; d="scan'208";a="88364176" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.81]) ([10.237.220.81]) by orsmga004.jf.intel.com with ESMTP; 17 May 2017 05:50:41 -0700 To: Thomas Monjalon , Gaetan Rivet Cc: dev@dpdk.org, Adrien Mazarguil , Neil Horman , Bruce Richardson , Stephen Hemminger References: <3248422.BZSJxlJxmA@xps13> From: Ferruh Yigit Message-ID: <09a808a2-2398-fc10-057c-b3595572e910@intel.com> Date: Wed, 17 May 2017 13:50:40 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <3248422.BZSJxlJxmA@xps13> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v2 00/13] introduce fail-safe PMD X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 May 2017 12:50:44 -0000 On 3/20/2017 3:00 PM, Thomas Monjalon wrote: > There have been some discussions on this new PMD and it will be > discussed today in the techboard meeting. > > I would like to expose my view and summarize the solutions I have heard. > First it is important to remind that everyone agrees on the need for > this feature, i.e. masking the hotplug events by maintaining an ethdev > object even without real underlying device. > > 1/ > The proposal from Gaetan is to add a failsafe driver with 2 features: > * masking underlying device > * limited and small failover code to switch from a device > to another one, with the same centralized configuration > The latter feature makes think to the bonding driver, but it could be > kept limited without any intent of implementing real bonding features. > > 2/ > If we really want to merge failsafe and bonding features, we could > create a new bonding driver with centralized configuration. > The legacy bonding driver let each slave to be configured separately. > It is a different model and we should not mix them. > If one is better, it could be deprecated later. > > 3/ > It can be tried to implement the failsafe feature into the bonding > driver, as Neil suggests. > However, I am not sure it would work very well or would be easy to use. > > 4/ > We can implement only the failsafe feature as a PMD and use it to wrap > the slaves of the bonding driver. > So the order of link would be > bonding -> failsafe -> real device > In this model, failsafe can have only one slave and do not implement > the fail-over feature. > Tech board decided [1] to "reconsider" the PMD for this release (17.08). So, lets start it J I think it is good idea to continue on top of above summary, is there a plan to how to proceed? Thanks, ferruh [1] http://dpdk.org/ml/archives/dev/2017-March/061009.html