Am 25.04.2017 11:06 schrieb "Gaëtan Rivet" <gaetan.ri...@6wind.com>:
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 removal >> 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, irrespective >> of an application handling this event. >> >> Signed-off-by: Gaetan Rivet <gaetan.ri...@6wind.com> >> Signed-off-by: Elad Persiko <ela...@mellanox.com> >> > > <...> > > 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 = >> Link status = >> Link status event = >> +Removal event = >> Queue status event = >> Rx interrupt = >> Free Tx mbuf on demand = >> > > 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 > -- Gaėtan Rivet 6WIND
