All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Zvi Effron <zeffron@riotgames.com>
To: Xdp <xdp-newbies@vger.kernel.org>
Subject: How to debug XDP_REDIRECT errors
Date: Sun, 20 Oct 2019 16:07:13 -0500	[thread overview]
Message-ID: <CAC1LvL3efhuf8dc-aQKepMND24drwVAHAzVs-4Np4CUTV8qOgQ@mail.gmail.com> (raw)

Hello,

I'm trying to get some additional performance out of XDP on the i40e
driver (under kernel 5.0.7, Fedora 28) by adjusting the queues to be
one per desired core. I have several cores isolated for network
traffic, so I'm adjusting the queues to be one per isolated core (with
IRQ adjustments to match) as opposed to the default of one per online
core. I've noticed that when I adjust the number of queues down, I see
packet loss proportional to the number of queues missing. For example,
if I drop the queues from the default of 36 down to 34, I see ~6%
packet loss.

Using the trace_pipe, I've managed to confirm that my program is
successfully calling bpf_redirect_map() for all of the packet (no
losst). I found the xdp_monitor tutorial[1] and ran it, and it shows
the loss showing up as XDP_REDIRECT errors (which I believe means the
raw_tracepoint xdp:xdp_redirect_map_err).

At this point, I'm a bit stuck on how to proceed further to determine
what is causing the redirect error and where the packet is being
dropped.

Any help in pointing me in the right direction for debugging
techniques would be greatly appreciated.

Thanks!
--Zvi

[1]: https://github.com/xdp-project/xdp-tutorial/blob/master/tracing02-xdp-monitor

             reply	other threads:[~2019-10-20 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-20 21:07 Zvi Effron [this message]
2019-10-21  4:04 ` How to debug XDP_REDIRECT errors Jesper Dangaard Brouer

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=CAC1LvL3efhuf8dc-aQKepMND24drwVAHAzVs-4Np4CUTV8qOgQ@mail.gmail.com \
    --to=zeffron@riotgames.com \
    --cc=xdp-newbies@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 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.