Hi
> -Original Message-
> From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
> Sent: Thursday, December 14, 2017 3:27 PM
> To: Matan Azrad
> Cc: Adrien Mazarguil ; Thomas Monjalon
> ; dev@dpdk.org; sta...@dpdk.org
> Subject: Re: [PATCH v2 4/4] net/failsafe: fix removed device handling
>
On Thu, Dec 14, 2017 at 01:07:31PM +, Matan Azrad wrote:
> Hi Gaetan
>
> > -Original Message-
> > From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
> > Sent: Thursday, December 14, 2017 12:49 PM
> > To: Matan Azrad
> > Cc: Adrien Mazarguil ; Thomas Monjalon
> > ; dev@dpdk.org; sta...
Hi Gaetan
> -Original Message-
> From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
> Sent: Thursday, December 14, 2017 12:49 PM
> To: Matan Azrad
> Cc: Adrien Mazarguil ; Thomas Monjalon
> ; dev@dpdk.org; sta...@dpdk.org
> Subject: Re: [PATCH v2 4/4] net/failsafe: fix removed device hand
On Thu, Dec 14, 2017 at 10:40:22AM +, Matan Azrad wrote:
> Hi Gaetan
>
> > >
> > > If you add this check in the iterator itself, you would skip removed
> > > devices before attempting operating upon them, right?
> > >
> > > Then it should probably help with your issue, unless you tested it
> -Original Message-
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Wednesday, December 13, 2017 7:09 PM
> To: Gaëtan Rivet ; Matan Azrad
>
> Cc: Adrien Mazarguil ; dev@dpdk.org;
> sta...@dpdk.org
> Subject: Re: [PATCH v2 4/4] net/failsafe: fix removed device handling
>
>
Hi Gaetan
> -Original Message-
> From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
> Sent: Wednesday, December 13, 2017 11:56 PM
> To: Matan Azrad
> Cc: Adrien Mazarguil ; Thomas Monjalon
> ; dev@dpdk.org; sta...@dpdk.org
> Subject: Re: [PATCH v2 4/4] net/failsafe: fix removed device han
Hi again Matan,
On Wed, Dec 13, 2017 at 05:09:16PM +0100, Gaëtan Rivet wrote:
> On Wed, Dec 13, 2017 at 03:48:46PM +, Matan Azrad wrote:
> > Hi Gaetan
> > Thanks for the review.
> > Some comments..
> >
> > > -Original Message-
> > > From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
>
13/12/2017 17:09, Gaëtan Rivet:
> On Wed, Dec 13, 2017 at 03:48:46PM +, Matan Azrad wrote:
> > From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
> > > > Fixes: a46f8d5 ("net/failsafe: add fail-safe PMD")
> > > > Fixes: b737a1e ("net/failsafe: support flow API")
> > > > Cc: sta...@dpdk.org
> >
On Wed, Dec 13, 2017 at 03:48:46PM +, Matan Azrad wrote:
> Hi Gaetan
> Thanks for the review.
> Some comments..
>
> > -Original Message-
> > From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
> > Sent: Wednesday, December 13, 2017 5:17 PM
> > To: Matan Azrad
> > Cc: Adrien Mazarguil ;
Hi Gaetan
Thanks for the review.
Some comments..
> -Original Message-
> From: Gaëtan Rivet [mailto:gaetan.ri...@6wind.com]
> Sent: Wednesday, December 13, 2017 5:17 PM
> To: Matan Azrad
> Cc: Adrien Mazarguil ; Thomas Monjalon
> ; dev@dpdk.org; sta...@dpdk.org
> Subject: Re: [PATCH v2 4/4
Hi Matan,
On Wed, Dec 13, 2017 at 02:29:30PM +, Matan Azrad wrote:
> There is time between the physical removal of the device until
> sub-device PMDs get a RMV interrupt. At this time DPDK PMDs and
> applications still don't know about the removal and may call sub-device
> control operation wh
There is time between the physical removal of the device until
sub-device PMDs get a RMV interrupt. At this time DPDK PMDs and
applications still don't know about the removal and may call sub-device
control operation which should return an error.
In previous code this error is reported to the appl
12 matches
Mail list logo