From: Ben Greear <greearb@candelatech.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Process level networking stats.
Date: Thu, 7 Mar 2024 20:20:23 -0800 [thread overview]
Message-ID: <efc8358d-e666-4ee6-95d1-a6ccae6949d9@candelatech.com> (raw)
In-Reply-To: <20240306195726.11a981cb@kernel.org>
On 3/6/24 19:57, Jakub Kicinski wrote:
> On Wed, 6 Mar 2024 14:57:55 -0800 Ben Greear wrote:
>> I am interested in a relatively straight-forward way to know the tx/rx bytes
>> sent/received by a process.
>
> What is "relatively straight-forward"? :)
> You could out the process in a cgroup and use cgroup hooks
>
The main thing is that I don't want to try to do it with packet capture.
Thanks for the suggestion of using cgroups. I will look into that.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2024-03-08 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 22:57 Process level networking stats Ben Greear
2024-03-07 3:57 ` Jakub Kicinski
2024-03-08 4:20 ` Ben Greear [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=efc8358d-e666-4ee6-95d1-a6ccae6949d9@candelatech.com \
--to=greearb@candelatech.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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).