netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: netdev@vger.kernel.org
Subject: [PATCH] Update the /proc/net/tcp documentation
Date: Mon, 15 Oct 2007 19:15:07 +0200	[thread overview]
Message-ID: <20071015191507.1750bc97@hyperion.delvare> (raw)

* Say that this interface is deprecated.
* Update function name references to match the current code.

Signed-off-by: Jean Delvare <khali@linux-fr.org>
---
Second version, updated based on Rick Jones' comments.

 Documentation/networking/proc_net_tcp.txt |    5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

--- linux-2.6.23-rc0.orig/Documentation/networking/proc_net_tcp.txt	2007-10-15 10:12:39.000000000 +0200
+++ linux-2.6.23-rc0/Documentation/networking/proc_net_tcp.txt	2007-10-15 19:11:57.000000000 +0200
@@ -1,8 +1,9 @@
 This document describes the interfaces /proc/net/tcp and /proc/net/tcp6.
+Note that these interfaces are deprecated in favor of tcp_diag.
 
 These /proc interfaces provide information about currently active TCP 
-connections, and are implemented by tcp_get_info() in net/ipv4/tcp_ipv4.c and
-tcp6_get_info() in net/ipv6/tcp_ipv6.c, respectively.
+connections, and are implemented by tcp4_seq_show() in net/ipv4/tcp_ipv4.c
+and tcp6_seq_show() in net/ipv6/tcp_ipv6.c, respectively.
 
 It will first list all listening TCP sockets, and next list all established
 TCP connections. A typical entry of /proc/net/tcp would look like this (split 


-- 
Jean Delvare

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15 17:15 Jean Delvare [this message]
2007-10-15 19:58 ` [PATCH] Update the /proc/net/tcp documentation David Miller

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=20071015191507.1750bc97@hyperion.delvare \
    --to=khali@linux-fr.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).