On 10/19/17, 9:56 AM, "ovs-dev-boun...@openvswitch.org on behalf of
antonio.fische...@intel.com" wrote:
In case a mempool name could not be generated log a message
and return a null mempool pointer to the caller.
CC: Mark B Kavanagh
CC: Darrell Ball
CC: Ciara Loftus
>From: Fischetti, Antonio
>Sent: Friday, October 20, 2017 10:38 AM
>To: Kavanagh, Mark B ; d...@openvswitch.org
>Cc: Darrell Ball ; Loftus, Ciara ;
>Kevin Traynor ; Aaron Conole
>Subject: RE: [PATCH v8 4/6] netdev-dpdk: manage failure in mempool name
>creation.
>
>
>
>> -Original Message-
> -Original Message-
> From: Kavanagh, Mark B
> Sent: Friday, October 20, 2017 10:28 AM
> To: Fischetti, Antonio ; d...@openvswitch.org
> Cc: Darrell Ball ; Loftus, Ciara ;
> Kevin Traynor ; Aaron Conole
> Subject: RE: [PATCH v8 4/6] netdev-dpdk: manage failure in mempool name
> creation
>From: Fischetti, Antonio
>Sent: Thursday, October 19, 2017 5:54 PM
>To: d...@openvswitch.org
>Cc: Kavanagh, Mark B ; Darrell Ball
>; Loftus, Ciara ; Kevin Traynor
>; Aaron Conole ; Fischetti, Antonio
>
>Subject: [PATCH v8 4/6] netdev-dpdk: manage failure in mempool name creation.
>
>In case a memp
On 10/19/2017 05:54 PM, antonio.fische...@intel.com wrote:
> In case a mempool name could not be generated log a message
> and return a null mempool pointer to the caller.
>
> CC: Mark B Kavanagh
> CC: Darrell Ball
> CC: Ciara Loftus
> CC: Kevin Traynor
> CC: Aaron Conole
> Fixes: d555d9bded5
> > -Original Message-
> > From: Stokes, Ian
> > Sent: Thursday, October 19, 2017 6:23 PM
> > To: Fischetti, Antonio ;
> > d...@openvswitch.org
> > Subject: RE: [ovs-dev] [PATCH v8 4/6] netdev-dpdk: manage failure in
> > mempool name creation.
>
> -Original Message-
> From: Stokes, Ian
> Sent: Thursday, October 19, 2017 6:23 PM
> To: Fischetti, Antonio ; d...@openvswitch.org
> Subject: RE: [ovs-dev] [PATCH v8 4/6] netdev-dpdk: manage failure in mempool
> name creation.
>
> > In case a mempool name c
> In case a mempool name could not be generated log a message and return a
> null mempool pointer to the caller.
>
Now that I look at this, is it the case that the issues have been resolved in
patches 1 and 2 but this is a clean up patch for something that might happen?
> CC: Mark B Kavanagh
In case a mempool name could not be generated log a message
and return a null mempool pointer to the caller.
CC: Mark B Kavanagh
CC: Darrell Ball
CC: Ciara Loftus
CC: Kevin Traynor
CC: Aaron Conole
Fixes: d555d9bded5f ("netdev-dpdk: Create separate memory pool for each port.")
Signed-off-by: