From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Trying to export per process network bandwidth stats under /proc/[pid]/
Date: Sat, 14 Jul 2018 08:41:51 +0200 [thread overview]
Message-ID: <20180714064151.GI20451@kroah.com> (raw)
In-Reply-To: <87in5iwlco.fsf@gmail.com>
On Sat, Jul 14, 2018 at 11:24:23AM +0800, Amos Bird wrote:
> Hello!
>
> I'm trying to add a proc entry under /proc/[pid] in order to get per process
> network bandwidth stats. I suppose it's similar to /proc/[pid]/io . However
> I couldn't find a modular way to add entries under /proc/[pid]. This thread https://lists.kernelnewbies.org/pipermail/kernelnewbies/2011-January/000475.html
> suggests modifying the kernel which isn't practical to me. Here is what I've
> found by going through a bit of the related kernel code.
>
> 1. I need to find a way to override or hooking `sock_sendmsg`/`sock_recvmsg`
> functions with accounting variables like `task_io_accounting`
> 2. a way to add proc entries under /proc/[pid] with readops printing
> `current` netio accounting variables.
>
> Am I on the right path of implementing this? Thanks!
Please don't do this in /proc, that way lies madness. There is code in
the android kernel tree that adds this type of process accounting to the
kernel, you should look at that. It's been rejected by upstream for
valid reasons, which you should be aware of, and is currently being
rewritten to use ebpf, which might be the better solution for you in the
long run.
And yes, you will have to modify the kernel to try to achieve this, but
it's better to just go grab the android code if you want to see how this
is done instead of trying to do it on your own from scratch.
hope this helps,
greg k-h
prev parent reply other threads:[~2018-07-14 6:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 3:24 Trying to export per process network bandwidth stats under /proc/[pid]/ Amos Bird
2018-07-14 6:41 ` Greg KH [this message]
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=20180714064151.GI20451@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.