From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <declan.doherty@intel.com>
Received: from mga06.intel.com (mga06.intel.com [134.134.136.31])
 by dpdk.org (Postfix) with ESMTP id D559D2C2A
 for <users@dpdk.org>; Thu, 29 Jun 2017 18:58:34 +0200 (CEST)
Received: from fmsmga002.fm.intel.com ([10.253.24.26])
 by orsmga104.jf.intel.com with ESMTP; 29 Jun 2017 09:58:33 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.40,282,1496127600"; d="scan'208";a="1188619793"
Received: from dwdohert-dpdk.ir.intel.com ([163.33.210.152])
 by fmsmga002.fm.intel.com with ESMTP; 29 Jun 2017 09:58:32 -0700
To: Alex Kiselev <kiselev99@gmail.com>, users <users@dpdk.org>
Cc: pablo.de.lara.guarch@intel.com, olivier.matz@6wind.com
References: <CAMKNYbzgjUKeAOPdMdY6CiW9cnFtEJHH-byG24WQH++mjy995g@mail.gmail.com>
From: Declan Doherty <declan.doherty@intel.com>
Message-ID: <7c44fb2e-c01b-95d5-2a2a-27b0f78136cc@intel.com>
Date: Thu, 29 Jun 2017 17:57:45 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <CAMKNYbzgjUKeAOPdMdY6CiW9cnFtEJHH-byG24WQH++mjy995g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-users] another fix to LACP mempool size
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jun 2017 16:58:35 -0000

On 29/06/17 13:11, Alex Kiselev wrote:
>> I am facing another issue with LACP LAG port.
>>
>> Jun 29 13:24:40 h4 the_router[24361]: PMD: Failed to allocate LACP
>> packet from pool
>>
>> There are thousands of such messages in the syslog.
>> ...
>> Alex Kiselev
> 
> It looks like It is the same issue that was descovered
> here http://dpdk.org/ml/archives/dev/2016-November/049971.html
> 
> Was there reasons not to include that patch into the main code?
> 

It looks like this slipped through the cracks on me, I think there was 
issues with another patch in that patchset at the time. I'll look at 
doing a rebase of this patch and the other one in that series 
(http://dpdk.org/dev/patchwork/patch/15093/) which has a fix for 
configuration propagation and re-post to the mailing list asap.