All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1415] Calling rte_eth_bond_8023ad_dedicated_queues_enable() leads to exhaustion of the LACP packet pool
Date: Thu, 11 Apr 2024 16:50:28 +0000	[thread overview]
Message-ID: <bug-1415-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1415

            Bug ID: 1415
           Summary: Calling rte_eth_bond_8023ad_dedicated_queues_enable()
                    leads to exhaustion of the LACP packet pool
           Product: DPDK
           Version: 23.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: michel@digirati.com.br
  Target Milestone: ---

When dedicated queues are enabled on a bond interface by calling
rte_eth_bond_8023ad_dedicated_queues_enable(), DPDK eventually starts
repeatedly loggin "tx_machine(580) - Failed to allocate LACP packet from pool".
According to the code of tx_machine(), this log entry means that the mbuf pool
created to send LACP packets (i.e. port->mbuf_pool) is exhausted.

The problem occurs about 10 minutes after my application (i.e.
https://github.com/AltraMayor/gatekeeper ) starts, and I can reproduce it with
one or two members in the bond interface. The problem does not occur if I
remove the call to rte_eth_bond_8023ad_dedicated_queues_enable().

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3240 bytes --]

                 reply	other threads:[~2024-04-11 16:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1415-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.