From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v2 1/5] ethdev: introduce device removal event
Date: Tue, 02 May 2017 11:18:06 +0200
Message-ID: <1493717377.6Zc0AIm2Fr@xps>
References: <cover.1492517222.git.gaetan.rivet@6wind.com>
 <20170425090536.GS14914@bidouze.vm.6wind.com>
 <CALe+Z03HZkGh8a41uyJU5BLhc=bjT5Wh2KD=-Nk1b8RyhNqMvA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: =?ISO-8859-1?Q?Ga=EBtan?= Rivet <gaetan.rivet@6wind.com>, dev@dpdk.org,
 Billy McFall <bmcfall@redhat.com>, Olivier MATZ <olivier.matz@6wind.com>,
 Ferruh Yigit <ferruh.yigit@intel.com>, Elad Persiko <eladpe@mellanox.com>
To: Jan Blunck <jblunck@infradead.org>
Return-path: <dev-bounces@dpdk.org>
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com
 [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id E3DC6377E
 for <dev@dpdk.org>; Tue,  2 May 2017 11:18:07 +0200 (CEST)
In-Reply-To: <CALe+Z03HZkGh8a41uyJU5BLhc=bjT5Wh2KD=-Nk1b8RyhNqMvA@mail.gmail.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

02/05/2017 09:35, Jan Blunck:
> Am 25.04.2017 11:06 schrieb "Ga=EBtan Rivet" <gaetan.rivet@6wind.com>:
>=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.