From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com [74.125.82.52]) by dpdk.org (Postfix) with ESMTP id 2FCB0133F for ; Mon, 20 Mar 2017 16:00:17 +0100 (CET) Received: by mail-wm0-f52.google.com with SMTP id t189so66860401wmt.1 for ; Mon, 20 Mar 2017 08:00:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=HbYm809lVZR/hXnULpenIzRYrKX9pSeda0V7S+lue4w=; b=hHk69XdA/djK31vZiqGPmKX/a/zu4vRr2Po27LPUQqgXTy0IONuUeuFBZJQfc9CI82 nqce3AYLinLv40iIdbJeDOu3rJBsJ3KfiWjMG3sooEE24egkWFJIUOFDBZhY2LP+v690 yW8ecyTIjwFXVqp7/wnGGL9SrrNlFTxK42Ee5gTMAqqW7hTx37/AzDmnznsOjqKWw+S9 4L7ccTELnOnTx+QzlzCum/TAN1Nhs75cFdml8MAEn+lr747Cr6WG2O5O8CUX+i2Lu8AG AbMWr1iAu1uQTwT3w7tlI/jD35VhW+RL2wNHnM7ca75DM+R5eQCTVKpzWE8B3DJP1uU4 9dog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=HbYm809lVZR/hXnULpenIzRYrKX9pSeda0V7S+lue4w=; b=Sn0ABeVMWPY+qwXAP8biQRhp3ubgIC9HrWPVtGvmyklydEckoVTvKcCxY6TtialMqw CTBJ1tSXqDlwgmCts6AVSaGre3K2EvWTJavLQfeRxb+sgVwEdJbZBR8XMvNoEBc7lsA+ JzWB+youdqnfMXlMZ6FCoFZunKODNg5kvdYJkuBb9cBvEaq38hGIspYN9fR1c5oRE4dv +lbIZtmtG1hioWTg20O2jJ9XUPOvXmDodRVgif0+avwYXweaP4H1EY9yYowjCYMujPKZ 1BQPB63UOUo6YfaM6eYQoaN8ZdsdmYrij8lIL/aOiJHaqbdrmqZYWOIwguNneGNptVUQ cN3A== X-Gm-Message-State: AFeK/H0lBT+ieetMxXQ8oS6nApecemtD8Ew06vlQu4YwpDmogYMrpyNPA0F9CBmKysE/jeLe X-Received: by 10.28.30.19 with SMTP id e19mr10390854wme.52.1490022016868; Mon, 20 Mar 2017 08:00:16 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id r2sm13765541wmb.26.2017.03.20.08.00.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Mar 2017 08:00:16 -0700 (PDT) From: Thomas Monjalon To: Gaetan Rivet Cc: dev@dpdk.org, Adrien Mazarguil Date: Mon, 20 Mar 2017 16:00:15 +0100 Message-ID: <3248422.BZSJxlJxmA@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Mon, 20 Mar 2017 15:00:17 -0000 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.