[dpdk-dev] [PATCH 3/4] net/bonding: another fix to LACP mempool size

2016-11-07 Thread Kulasek, TomaszX
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Robert Sanford > Sent: Monday, August 1, 2016 22:43 > To: dev at dpdk.org > Cc: Doherty, Declan ; De Lara Guarch, Pablo > ; olivier.matz at 6wind.com > Subject: [dpdk-dev] [PATCH 3/4] net

[dpdk-dev] [PATCH 3/4] net/bonding: another fix to LACP mempool size

2016-08-24 Thread Olivier MATZ
Hi Robert, On 08/23/2016 10:01 PM, Sanford, Robert wrote: > Hi Olivier, > > On 8/23/16, 11:09 AM, "Olivier MATZ" wrote: > > Hi Robert, > > On 08/01/2016 10:42 PM, Robert Sanford wrote: > > The following log message may appear after a slave is idle (or nearly > > idle) for a

[dpdk-dev] [PATCH 3/4] net/bonding: another fix to LACP mempool size

2016-08-23 Thread Sanford, Robert
Hi Olivier, On 8/23/16, 11:09 AM, "Olivier MATZ" wrote: Hi Robert, On 08/01/2016 10:42 PM, Robert Sanford wrote: > The following log message may appear after a slave is idle (or nearly > idle) for a few minutes: "PMD: Failed to allocate LACP packet from > pool". > >

[dpdk-dev] [PATCH 3/4] net/bonding: another fix to LACP mempool size

2016-08-23 Thread Olivier MATZ
Hi Robert, On 08/01/2016 10:42 PM, Robert Sanford wrote: > The following log message may appear after a slave is idle (or nearly > idle) for a few minutes: "PMD: Failed to allocate LACP packet from > pool". > > Problem: All mbufs from a slave's private pool (used exclusively for > transmitting

[dpdk-dev] [PATCH 3/4] net/bonding: another fix to LACP mempool size

2016-08-01 Thread Robert Sanford
The following log message may appear after a slave is idle (or nearly idle) for a few minutes: "PMD: Failed to allocate LACP packet from pool". Problem: All mbufs from a slave's private pool (used exclusively for transmitting LACPDUs) have been allocated and are still sitting in the device's tx