From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f48.google.com (mail-pg0-f48.google.com [74.125.83.48]) by dpdk.org (Postfix) with ESMTP id 6411B2952 for ; Fri, 3 Mar 2017 18:27:29 +0100 (CET) Received: by mail-pg0-f48.google.com with SMTP id b129so46004441pgc.2 for ; Fri, 03 Mar 2017 09:27:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Gfka2q8pEVTH3CsigP5EsBJvqbP+0DGijCd6c0CxNao=; b=E8bYBqEaNYNIzyzMto3p7JQ6kTjFuyZZE4FoYx8Cv8qcmOn5Sa5+kOL6JJEfk//67R 791+7B/TkXAoDkE1z00Q4a9CaCs45nlCVkv3HbtV20aV7xG6jnyriF8iOQGqg2gwPzCw sqh3bmBg+JK5eqrLb/nDmbEdLPJ1z4/ke6/NjOhnBGMrUxofmRYZ/K9vN5XRfzI35zql mfBfZQ+jjbLhGzzy651PnkYLlqx/l0MZ006KyOl5UIva98HKFuniQm6oVGeEY2687BcY f53LaWg6TVQ0kcafqlovCsZqNnjkOhD1ulTz111V1QRgEQlEXSQrhAaj4n+2HtUSMbRz BUQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Gfka2q8pEVTH3CsigP5EsBJvqbP+0DGijCd6c0CxNao=; b=fUphpfZrG85ufN1au+FVJqKXA4VMoVrLe0L7k9cR55a04xXBPirxNHU6VOHa+hfuy6 hz0lqrNvu5hl5iYPSBC7u1J4xOwKG2OxehK3FK+rNJDVhBlbdbaoWGgylCGm6IkG2wM5 ieHoDMCjixZkNFPzMZXJ7tHCJvafrx6Bv422cORRHoefw5xn7M1LlTrTCz2IWW6DExt+ IDSD6ysIhNSGNeX+T2m9v5mykmj0qT/O2JxqA842MYAalgvZjWmlUqU6q81A3EszxKpC qLbYIBJoGdVDVvvce4KsJ37kabg+ORZSxR0mD9B3NOkHO/ysvwQxE+NHD4XL1sXEnyxG vFIw== X-Gm-Message-State: AMke39l9FXhPMkO65AnyMuapB90zUoFk2pInnXxMnxEarDiecY8KLuSXut1KduzqFkt8bg== X-Received: by 10.98.25.202 with SMTP id 193mr4934728pfz.134.1488562048374; Fri, 03 Mar 2017 09:27:28 -0800 (PST) Received: from xeon-e3 (204-195-18-65.wavecable.com. [204.195.18.65]) by smtp.gmail.com with ESMTPSA id r134sm24545427pfr.83.2017.03.03.09.27.28 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 03 Mar 2017 09:27:28 -0800 (PST) Date: Fri, 3 Mar 2017 09:27:21 -0800 From: Stephen Hemminger To: Gaetan Rivet Cc: dev@dpdk.org, Thomas Monjalon , Adrien Mazarguil , Jingjing Wu Message-ID: <20170303092721.7033b660@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH 00/12] 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: Fri, 03 Mar 2017 17:27:29 -0000 On Fri, 3 Mar 2017 16:40:22 +0100 Gaetan Rivet wrote: > This PMD intercepts and manages Ethernet device removal events issued by > slave PMDs and re-initializes them transparently when brought back so that > existing applications do not need to be modified to benefit from true > hot-plugging support. > > The stacked PMD approach shares many similarities with the bonding PMD but > with a different purpose. While bonding provides the ability to group > several links into a single logical device for enhanced throughput and > supports fail-over at link level, this one manages the sudden disappearance > of the underlying device; it guarantees applications face a valid device in > working order at all times. > > Each fail-safe instance is configured to run atop one or several > devices, with one defined as the preferred device. Hot-plug events are > handled on all of them, and Tx is always directed to the preferred device > if present or to the next available failover device (Rx is always performed > on all devices for simplicity). > > Moreover, the configured slaves (preferred or failover) do not need to be > present at initialization time and may appear later. > > Slaves configuration is continuously synchronized with that of the virtual > device, which exposes their common set of capabilities to the application. > Failure to apply the current configuration state to a slave for any reason > simply reschedules its initialization. > This looks interesting for SR-IOV VF support on Hyper-V. It would be good if the driver worked in interrupt mode as well.