DPDK usage discussions
 help / color / mirror / Atom feed
From: Kyle Larose <klarose@sandvine.com>
To: Alex Kiselev <kiselev99@gmail.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] link bonding driver, lacp mode
Date: Thu, 29 Jun 2017 13:06:35 +0000	[thread overview]
Message-ID: <D76BBBCF97F57144BB5FCF08007244A7705F36B1@wtl-exchp-1.sandvine.com> (raw)
In-Reply-To: <CAMKNYbyFuOa+R4r6qWcdm3x-XoT_MfJ+4rxF0tWBdrbhyyccAw@mail.gmail.com>

Hey Alex,

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Alex Kiselev
> Sent: Thursday, June 29, 2017 6:50 AM
> To: users
> Subject: [dpdk-users] link bonding driver, lacp mode
> 
> Hello.
> 
> 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.
> But my app was working ok at the same time.
> The mbuf pool that is used to setup rx queues (rte_eth_rx_queue_setup) was
> ok too.
> 
> So, is it a mbuf leak in the bonding driver?
> 
> 
> P.S.
> Does anybody have a success story working with LACP bonding ports?
> 

I've been able to get it working, but I was always transmitting. I'm not sure if I'd run into the issue you mentioned in your later email.

> 
> --
> Alex Kiselev

  reply	other threads:[~2017-06-29 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 10:49 Alex Kiselev
2017-06-29 13:06 ` Kyle Larose [this message]
2017-06-29 14:30   ` Alex Kiselev
  -- strict thread matches above, loose matches on Subject: below --
2017-06-28 10:52 Alex Kiselev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D76BBBCF97F57144BB5FCF08007244A7705F36B1@wtl-exchp-1.sandvine.com \
    --to=klarose@sandvine.com \
    --cc=kiselev99@gmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).