From: David Ahern <dsahern@gmail.com>
To: bjorn.topel@gmail.com, netdev@vger.kernel.org,
stephen@networkplumber.org
Cc: "Björn Töpel" <bjorn.topel@intel.com>,
magnus.karlsson@intel.com, magnus.karlsson@gmail.com
Subject: Re: [PATCH iproute2-next v2] ss: add AF_XDP support
Date: Wed, 30 Jan 2019 22:01:46 -0700 [thread overview]
Message-ID: <377c0c78-2eb2-5662-f4cb-a9286feab0d1@gmail.com> (raw)
In-Reply-To: <20190130065732.22910-1-bjorn.topel@gmail.com>
On 1/29/19 11:57 PM, bjorn.topel@gmail.com wrote:
> From: Björn Töpel <bjorn.topel@intel.com>
>
> AF_XDP is an address family that is optimized for high performance
> packet processing.
>
> This patch adds AF_XDP support to ss(8) so that sockets can be queried
> and monitored.
>
> Example:
> $ sudo ss --xdp -e -p -m
> Recv-Q Send-Q Local Address:Port Peer Address:Port
>
> 0 0 enp134s0f0:q20 *
> users:(("xdpsock",pid=17787,fd=3)) ino:39424 sk:4
> rx(entries:2048)
> tx(entries:2048)
> umem(id:1,size:8388608,num_pages:2048,chunk_size:2048,headroom:0,ifindex:7,
> qid:20,zc:0,refs:1)
> fr(entries:2048)
> cr(entries:2048) skmem:(r0,rb212992,t0,tb212992,f0,w0,o0,bl0,d0)
> 0 0 enp24s0f0:q0 *
> users:(("xdpsock",pid=17780,fd=3)) ino:37384 sk:5
> rx(entries:2048)
> tx(entries:2048)
> umem(id:0,size:8388608,num_pages:2048,chunk_size:2048,headroom:0,ifindex:6,
> qid:0,zc:1,refs:1)
> fr(entries:2048)
> cr(entries:2048) skmem:(r0,rb212992,t0,tb212992,f0,w0,o0,bl0,d0)
>
> Signed-off-by: Björn Töpel <bjorn.topel@intel.com>
> ---
> v1->v2:
> * Define/redefine AF_XDP/AF_MAX if missing. (David)
> * Add example to the commit log. (David)
> ---
> include/utils.h | 8 +++
> man/man8/ss.8 | 9 ++-
> misc/ss.c | 168 +++++++++++++++++++++++++++++++++++++++++++++++-
> 3 files changed, 180 insertions(+), 5 deletions(-)
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2019-01-31 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 6:57 [PATCH iproute2-next v2] ss: add AF_XDP support bjorn.topel
2019-01-31 5:01 ` David Ahern [this message]
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=377c0c78-2eb2-5662-f4cb-a9286feab0d1@gmail.com \
--to=dsahern@gmail.com \
--cc=bjorn.topel@gmail.com \
--cc=bjorn.topel@intel.com \
--cc=magnus.karlsson@gmail.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).