Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Robert Hogan <robert@roberthogan.net>
To: netfilter@lists.netfilter.org
Subject: i/o stats per inode in /proc/net/tcp
Date: Sun, 15 Apr 2007 10:10:17 +0100	[thread overview]
Message-ID: <200704151010.17573.robert@roberthogan.net> (raw)

This may be a more appropriate question for lkml, but:

Why does /proc/net/tcp not give i/o stats per inode? Briefly looking at 
tcp_ipv4.c and co., it seems none of the sock structures associated with a 
tcp sock contain i/o counters so it may be reasons of non-triviality. That 
said, it does seem as if tcp_input.c and tcp_output.c could implement 
counting if there was a counter available in tcp_sock or the like.

Is there another /proc file that can be used in conjuction with /proc/net/tcp 
to gather per inode i/o stats? 

It just seems like such a natural thing to offer - as a user I'm always 
wondering where that little trickle of i/o on my bw monitor is coming from.

Can someone enlighten me?


Thanks,
Robert


             reply	other threads:[~2007-04-15  9:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-15  9:10 Robert Hogan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-04-15  9:13 i/o stats per inode in /proc/net/tcp Robert Hogan

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=200704151010.17573.robert@roberthogan.net \
    --to=robert@roberthogan.net \
    --cc=netfilter@lists.netfilter.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