From: Brenden Blanco <bblanco@gmail.com>
To: Alexander Duyck <alexander.h.duyck@intel.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
John Fastabend <john.fastabend@gmail.com>
Cc: netdev@vger.kernel.org
Subject: ixgbe tx hang with XDP_TX beyond queue limit
Date: Thu, 8 Jun 2017 23:22:29 -0700 [thread overview]
Message-ID: <20170609062228.GA14897@gmail.com> (raw)
Hi,
I am doing some XDP testing on a dual socket, combined 40 core machine
with ixgbe. I have found that with the default settings, depending on
which core a packet is received on, the xdp tx queue will hang with:
ixgbe 0000:01:00.0 eno1: Detected Tx Unit Hang (XDP)
Tx Queue <38>
TDH, TDT <0>, <8>
next_to_use <8>
next_to_clean <0>
tx_buffer_info[next_to_clean]
time_stamp <0>
jiffies <101f21bb8>
ixgbe 0000:01:00.0 eno1: tx hang 1 detected on queue 38, resetting adapter
ixgbe 0000:01:00.0 eno1: initiating reset due to tx timeout
ixgbe 0000:01:00.0 eno1: Reset adapter
When the received core is such that the xdp queue falls beyond
MAX_TX_QUEUES, then the hang results. In other words, if I leave
`ethtool -L eno1 combined 40` (the default), and a packet is received on
core 24 or greater, it hangs. However, if I lower the tx queue count to
24 (since XDP is forced to nr_cpu_ids), or if I force the incoming
packets onto core < 24 with an ntuple filter, then no hang occurs.
I imagine that some limits on the number of queues is in order here, or
some error reporting when loading the xdp program/allocating queues.
For now I am working around by lowering the rx queue count to leave
space for the xdp queues.
Thanks,
Brenden
reply other threads:[~2017-06-09 6:23 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=20170609062228.GA14897@gmail.com \
--to=bblanco@gmail.com \
--cc=alexander.h.duyck@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.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).