From: David Miller <davem@davemloft.net>
To: yamato@redhat.com
Cc: netdev@vger.kernel.org
Subject: Re: Adding inode field to /proc/net/netlink
Date: Sun, 28 Feb 2010 01:00:57 -0800 (PST) [thread overview]
Message-ID: <20100228.010057.229746532.davem@davemloft.net> (raw)
In-Reply-To: <20100228.144537.445518512048328806.yamato@redhat.com>
From: Masatake YAMATO <yamato@redhat.com>
Date: Sun, 28 Feb 2010 14:45:37 +0900 (JST)
> The Inode field in /proc/net/{tcp,udp,packet,raw,...} is useful to know the types of
> file descriptors associated to a process. Actually lsof utility uses the field.
> Unfortunately, unlike /proc/net/{tcp,udp,packet,raw,...}, /proc/net/netlink doesn't have the field.
> This patch adds the field to /proc/net/netlink.
>
> Signed-off-by: Masatake YAMATO <yamato@redhat.com>
Unfortunately we cannot add new fields without breaking the parsing
done by existing applications.
Sorry.
next prev parent reply other threads:[~2010-02-28 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 5:45 Adding inode field to /proc/net/netlink Masatake YAMATO
2010-02-28 9:00 ` David Miller [this message]
2010-02-28 9:13 ` Eric Dumazet
2010-02-28 9:28 ` David Miller
2010-02-28 9:50 ` Masatake YAMATO
2010-02-28 9:44 ` Eric Dumazet
2010-02-28 12:44 ` Masatake YAMATO
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=20100228.010057.229746532.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yamato@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