netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Claudi <aclaudi@redhat.com>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, dsahern@gmail.com
Subject: [PATCH iproute2-next 0/2] ss: remove implicit dependency on rpcinfo
Date: Wed, 16 Mar 2022 19:52:12 +0100	[thread overview]
Message-ID: <cover.1647455133.git.aclaudi@redhat.com> (raw)

ss uses rpcinfo to get info about rpc service sockets. However, rpcinfo
is not part of iproute2 and it's an implicit dependency for ss.

This series uses libtirpc[1] API to implement the same feature of
rpcinfo for ss. This makes it possible to get info about rpc sockets,
provided ss is compiled with libtirpc support.

As a nice byproduct, this makes ss provide info about some ipv6 rpc
sockets that are not displayed using 'rpcinfo -p'.

- patch 1 adds a configure function to check for libtirpc;
- patch 2 actually rework ss to use libtirpc.

[1] https://git.linux-nfs.org/?p=steved/libtirpc.git

Andrea Claudi (2):
  configure: add check_libtirpc()
  ss: remove an implicit dependency on rpcinfo

 configure | 16 ++++++++++
 misc/ss.c | 93 +++++++++++++++++++++++++++++++++++++++++++------------
 2 files changed, 89 insertions(+), 20 deletions(-)

-- 
2.35.1


             reply	other threads:[~2022-03-16 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-16 18:52 Andrea Claudi [this message]
2022-03-16 18:52 ` [PATCH iproute2-next 1/2] configure: add check_libtirpc() Andrea Claudi
2022-03-16 18:52 ` [PATCH iproute2-next 2/2] ss: remove an implicit dependency on rpcinfo Andrea Claudi
2022-03-24  3:30 ` [PATCH iproute2-next 0/2] ss: remove " patchwork-bot+netdevbpf

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=cover.1647455133.git.aclaudi@redhat.com \
    --to=aclaudi@redhat.com \
    --cc=dsahern@gmail.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).