From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id E3DC6377E for ; Tue, 2 May 2017 11:18:07 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 72C3A20B7F; Tue, 2 May 2017 05:18:07 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Tue, 02 May 2017 05:18:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=FIOvUozMcX1sz2X aSkNJxdBhLeMv4g5XTrTYA72WFq0=; b=Ll1uWnMIys0P5S7SUXxXTYpdL5tGOYz vSjoebqvjprUuTuXB4Iraha6fzP4aJH7dciGmM/vFqK5KXg1EcoBqwZZW3cSBJ5k Ic85IprN2qe2IoYn9Rl7R1bXtOoaoYr+Uuw+h08YH+RNaRGh8OMns/fCwSLD2md7 OF33lIHz01iE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=FIOvUozMcX1sz2XaSkNJxdBhLeMv4g5XTrTYA72WFq0=; b=KMYmoHSY /AUX8xLFYCYNxq11wfl/Ggoz7nHDFYpizodKf8aWRuBwT1tWTmOwXRrM/FONIFB7 NKLh1RMENRWGozz9nDeGmcYs+QBMoJnR0KnMVddYEnlMSwjQD1zkk33+u2mzuG1a DDePzsloVP6ULZBlJOi18VbvECbifYu+rWSOKyEHCIQP68vBZujz42kiMKnDKsT9 P7rUy3U7/gQGYYX48brQt0ln2fB42aDn2Kpo/aif0ZsPVNwNECpqNSgQwTFC3SLQ CnzINL8KhHLvMOOKCK9U61RViw6McZxX6Huyv1q3h+mAPvt3IpBkaEt/9lxoISNC H07QPr+JSAa25g== X-ME-Sender: X-Sasl-enc: Wicwd8kOsDioVmIfUvnBjDGAaANdh1F8nMM7IjjQoRYF 1493716687 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 2C6792473A; Tue, 2 May 2017 05:18:07 -0400 (EDT) From: Thomas Monjalon To: Jan Blunck Cc: =?ISO-8859-1?Q?Ga=EBtan?= Rivet , dev@dpdk.org, Billy McFall , Olivier MATZ , Ferruh Yigit , Elad Persiko Date: Tue, 02 May 2017 11:18:06 +0200 Message-ID: <1493717377.6Zc0AIm2Fr@xps> In-Reply-To: References: <20170425090536.GS14914@bidouze.vm.6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-dev] [PATCH v2 1/5] ethdev: introduce device removal event 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: Tue, 02 May 2017 09:18:08 -0000 02/05/2017 09:35, Jan Blunck: > Am 25.04.2017 11:06 schrieb "Ga=EBtan Rivet" : >=20 > Hi Ferruh, >=20 >=20 > On Fri, Apr 21, 2017 at 03:59:24PM +0100, Ferruh Yigit wrote: >=20 > > On 4/18/2017 1:17 PM, Gaetan Rivet wrote: > > > >> This new API allows reacting to a device removal. > >> A device removal is the sudden disappearance of a device from its > >> bus. > >> > > > I don't think this belongs into ethdev. If it is bus related we need to > expose this from it so that apps can register for the low level device > being unplugged. Yes it sounds right. We could work on device notifications. We need to find a way of notifying the application that there is a device event and that it affects one or more port at ethdev/cryptodev/eventdev level.