From: Matthew Hall <mh@mhcomputing.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: per-PID network stats files in /proc
Date: Tue, 24 Sep 2013 14:22:39 -0700 [thread overview]
Message-ID: <20130924212238.GA6673@mhcomputing.net> (raw)
In-Reply-To: <20130924140435.5881cf76@nehalam.linuxnetplumber.net>
On Tue, Sep 24, 2013 at 02:04:35PM -0700, Stephen Hemminger wrote:
> You could do what you want by putting each process in own network
> namespace, but that might be more work than you want to bother with.
Putting my one process or group of processes into one namespace, separate from
the one the rest of the system uses, could be perfectly OK actually.
So I'm going to look into this and see if it's possible. At least it would
give me a better route than where I am right now.
Thanks!
Matthew.
next prev parent reply other threads:[~2013-09-24 21:24 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
2013-09-24 21:04 ` Stephen Hemminger
2013-09-24 21:22 ` Matthew Hall [this message]
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=20130924212238.GA6673@mhcomputing.net \
--to=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;
as well as URLs for NNTP newsgroup(s).