From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f178.google.com (mail-wr0-f178.google.com [209.85.128.178]) by dpdk.org (Postfix) with ESMTP id C5C55F72 for ; Tue, 2 May 2017 09:35:39 +0200 (CEST) Received: by mail-wr0-f178.google.com with SMTP id w50so73609558wrc.0 for ; Tue, 02 May 2017 00:35:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AEpY0c421nspVfEgz0I2a5Mtr9siu9rH2mgu3LuHf+k=; b=pAmmtmgO2ZWo3dabxH5lYIWz2DAFrfS0/cnf/3lfEufH81Yt59YOgnsNFlFXt8StWJ qZhdKKh/JqNRvfEo0oBAwxX4NdQnybVB0o51F5uE+tLg37GivDyTFxqgechsv3Y9HbJp ztO3Fu3ilBiGzAjS+tOGfoxBk6jt6O1GKQmign8ZqKAGYUrbicLTOPu3VhUOic9c8Eoj ZxB0887h8YEMM9JELVJJQWTEWhULTBkrYjg0Y/Q0A2x0vz2WJsEW9txHtDX5KH3CX4ID NN3wnjX1+AFpuwmhFiYDenr2ASfF+zCu6f41zRg4nIorHijHIIzB0ga6qQPJbTFo/ul3 osGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AEpY0c421nspVfEgz0I2a5Mtr9siu9rH2mgu3LuHf+k=; b=OBSfWk9I8pi7JFt0AcV/icup72SHgsvN5ram+vawGvAapr7b7oOAfdRZNpiRNkLIjT pOW6QJdUxh8MNntu2iFulb3arm2Mn3yuvXWo1uSJ34Sh99L+n4Y6p5b1wVkitcBU5XQa 58gUNb8ycEq0t4xwoKTcv4OCgqVpSFu3qAXJSzwM3DM0VtE1J+Uv74qPzaGqVo5B/xMQ sVB8TKQWoy8qkdKdp0Y+xixCebh9dBXQuR+d6cMguWPHroDbOfB9Qxe+ysIAw1O+AWpU lYwl1J8VOXqs593uq83hv59TOvTups0Oe95AF+IqOkphGhZzeChSz4jawnePK80wHiqW s3RQ== X-Gm-Message-State: AN3rC/5fk+7uQV+ibGdcgr000Z/Iv5kuDw3RGLvdJ8qaapfXLFiSoBxq SmKuedGi6hGO2Z79+WXWMUWT13iDEQ== X-Received: by 10.223.143.13 with SMTP id p13mr18018131wrb.3.1493710539498; Tue, 02 May 2017 00:35:39 -0700 (PDT) MIME-Version: 1.0 Sender: jblunck@gmail.com Received: by 10.28.132.11 with HTTP; Tue, 2 May 2017 00:35:38 -0700 (PDT) Received: by 10.28.132.11 with HTTP; Tue, 2 May 2017 00:35:38 -0700 (PDT) In-Reply-To: <20170425090536.GS14914@bidouze.vm.6wind.com> References: <923e5a49-6514-4a28-fb89-81e196ae99c9@intel.com> <20170425090536.GS14914@bidouze.vm.6wind.com> From: Jan Blunck Date: Tue, 2 May 2017 09:35:38 +0200 X-Google-Sender-Auth: hMom8MX-rgSY-G2Q5LjZU4kTHh0 Message-ID: To: =?UTF-8?Q?Ga=C3=ABtan_Rivet?= Cc: dev , Billy McFall , Olivier MATZ , Ferruh Yigit , Elad Persiko , Thomas Monjalon Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 07:35:40 -0000 Am 25.04.2017 11:06 schrieb "Ga=C3=ABtan Rivet" : Hi Ferruh, On Fri, Apr 21, 2017 at 03:59:24PM +0100, Ferruh Yigit wrote: > 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. Jan >> PMDs implementing support for this notification guarantee that the remov= al >> of the underlying device does not incur a risk to the application. >> >> In particular, Rx/Tx bursts and all other functions can still be called >> (albeit likely returning errors) without triggering a crash, irrespectiv= e >> of an application handling this event. >> >> Signed-off-by: Gaetan Rivet >> Signed-off-by: Elad Persiko >> > > <...> > > diff --git a/doc/guides/nics/features/default.ini >> b/doc/guides/nics/features/default.ini >> index b1b9114..cafc6c7 100644 >> --- a/doc/guides/nics/features/default.ini >> +++ b/doc/guides/nics/features/default.ini >> @@ -10,6 +10,7 @@ >> Speed capabilities =3D >> Link status =3D >> Link status event =3D >> +Removal event =3D >> Queue status event =3D >> Rx interrupt =3D >> Free Tx mbuf on demand =3D >> > > This release a few NIC features added, and it is hard to follow them if > you are particularly looking for these features. > > So do you think does it make sense to put those new PMD features into > release notes to make it more visible? > > Yes it seems like a good idea to announce this evolution. I will send the relevant patch for this soon. Thanks, > ferruh > --=20 Ga=C4=97tan Rivet 6WIND