From: Ciara Loftus <ciara.loftus@intel.com>
To: bpf@vger.kernel.org, bjorn.topel@intel.com, magnus.karlsson@intel.com
Cc: Ciara Loftus <ciara.loftus@intel.com>
Subject: [PATCH bpf-next 0/3] xsk: add new statistics
Date: Wed, 8 Jul 2020 07:28:32 +0000 [thread overview]
Message-ID: <20200708072835.4427-1-ciara.loftus@intel.com> (raw)
This series introduces new statistics for af_xdp:
1. drops due to rx ring being full
2. drops due to fill ring being empty
3. failures pulling an item from the tx ring
These statistics should assist users debugging and troubleshooting
peformance issues and packet drops.
The statistics are made available though the getsockopt and xsk_diag
interfaces, and the ability to dump these extended statistics is made
available in the xdpsock application via the --extra-stats or -x flag.
A separate patch which will add ss/iproute2 support will follow.
Ciara Loftus (3):
xsk: add new statistics
samples: bpf: add an option for printing extra statistics in xdpsock
xsk: add xdp statistics to xsk_diag
include/net/xdp_sock.h | 4 ++
include/uapi/linux/if_xdp.h | 5 +-
include/uapi/linux/xdp_diag.h | 11 ++++
net/xdp/xsk.c | 36 +++++++++++--
net/xdp/xsk_buff_pool.c | 1 +
net/xdp/xsk_diag.c | 17 ++++++
net/xdp/xsk_queue.h | 6 +++
samples/bpf/xdpsock_user.c | 87 ++++++++++++++++++++++++++++++-
tools/include/uapi/linux/if_xdp.h | 5 +-
9 files changed, 163 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2020-07-08 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 7:28 Ciara Loftus [this message]
2020-07-08 7:28 ` [PATCH bpf-next 1/3] xsk: add new statistics Ciara Loftus
2020-07-08 7:28 ` [PATCH bpf-next 2/3] samples: bpf: add an option for printing extra statistics in xdpsock Ciara Loftus
2020-07-08 7:28 ` [PATCH bpf-next 3/3] xsk: add xdp statistics to xsk_diag Ciara Loftus
2020-07-08 11:18 ` [PATCH bpf-next 0/3] xsk: add new statistics Björn Töpel
2020-07-13 22:36 ` Alexei Starovoitov
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=20200708072835.4427-1-ciara.loftus@intel.com \
--to=ciara.loftus@intel.com \
--cc=bjorn.topel@intel.com \
--cc=bpf@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
/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).