From: Stephen Hemminger <stephen@networkplumber.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Jorgen Hansen <jhansen@vmware.com>
Subject: Re: Use sock_diag instead of procfs for new address families?
Date: Tue, 18 Jul 2017 09:58:38 -0700 [thread overview]
Message-ID: <20170718095838.18afb608@xeon-e3> (raw)
In-Reply-To: <20170718161806.GA21151@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
On Tue, 18 Jul 2017 17:18:06 +0100
Stefan Hajnoczi <stefanha@redhat.com> wrote:
> I am implementing userspace access to socket information for AF_VSOCK.
> A few hours into writing and testing a /proc/net/vsock seq_file I
> noticed that ss(8) prefers NETLINK_SOCK_DIAG over procfs.
>
> Before potentially wasting time implementing a legacy interface that
> won't be accepted, I thought it might be good to ask :).
>
> Which approach is preferred?
> 1. New address families must implement only sock_diag.
> 2. Both sock_diag and procfs must be implemented.
> 3. Implement whichever interface you prefer.
>
> Thanks,
> Stefan
You are correct, I am unlikely to take any new code using /proc
in ss.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-18 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 16:18 Use sock_diag instead of procfs for new address families? Stefan Hajnoczi
2017-07-18 16:58 ` Stephen Hemminger [this message]
2017-07-19 8:48 ` Stefan Hajnoczi
2017-07-18 17:46 ` David Miller
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=20170718095838.18afb608@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=jhansen@vmware.com \
--cc=netdev@vger.kernel.org \
--cc=stefanha@redhat.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).