From: Eric Dumazet <eric.dumazet@gmail.com>
To: Matthew Hall <mh@mhcomputing.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>, netdev@vger.kernel.org
Subject: Re: per-PID network stats files in /proc
Date: Tue, 24 Sep 2013 14:02:29 -0700 [thread overview]
Message-ID: <1380056549.3165.117.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130924204442.GA5074@mhcomputing.net>
On Tue, 2013-09-24 at 13:44 -0700, Matthew Hall wrote:
> On Tue, Sep 24, 2013 at 01:41:57PM -0700, Stephen Hemminger wrote:
> > No. because most of these would be associated with global state.
> > Even sockets can be shared between PID's.
>
> OK. So if this is true, then I feel compelled to ask, why does
> /proc/PID/net/snmp exist in the first place, if it would never really work?
That because of network containers
You can perfectly use a network container to get your own copy of
counters
ip netns help
next prev parent reply other threads:[~2013-09-24 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-24 20:15 per-PID network stats files in /proc Matthew Hall
2013-09-24 20:41 ` Stephen Hemminger
2013-09-24 20:44 ` Matthew Hall
2013-09-24 21:02 ` Eric Dumazet [this message]
2013-09-24 21:04 ` Stephen Hemminger
2013-09-24 21:22 ` Matthew Hall
2013-09-26 20:12 ` Matthew Hall
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=1380056549.3165.117.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=mh@mhcomputing.net \
--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