From: Rick Jones <rick.jones2@hp.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: Eric Dumazet <dada1@cosmosbay.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] include listenq max backlog in /proc/net/tcp and include in tcp_info
Date: Tue, 11 Sep 2007 11:10:11 -0700 [thread overview]
Message-ID: <46E6DA03.2040602@hp.com> (raw)
In-Reply-To: <1189532811.19000.6.camel@w-sridhar2.beaverton.ibm.com>
>>>>BTW, what do people think about doing the same thing with the rxqueue
>>>>and txqueue's of netstat output?
>>>>
>>>
>>>
>>>I dont understand this question, I thought your patch already handled this
>>>(for the txqueue, since rxqueue is already there), as netstat uses
>>>/proc/net/tcp (unfortunatly)
>>
>>Well, it doesn't seem to be the case. This is from the same system as
>>the ss output above:
>>
>>hpcpc103:~# netstat -an | grep LISTEN
>>tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
>>tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN
>>tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
>>tcp 0 0 0.0.0.0:42137 0.0.0.0:* LISTEN
>>tcp6 0 0 :::22 :::* LISTEN
>>unix 2 [ ACC ] STREAM LISTENING 5666 /var/run/acpid.socket
>>
>>I thought I saw some other code in there when I was stumbling around.
>
>
> Yes. netstat code seems to have a explicit check for TCP_LISTEN state
> and zeroing txq and rxq.
>>From tcp_do_one() in netstat.c
> if (state == TCP_LISTEN) {
> time_len = 0;
> retr = 0L;
> rxq = 0L;
> txq = 0L;
> }
How terribly cheeky of them. I wonder why they were doing that?
> We should fix this. Also i think it is a good idea to update netstat to use
> INET_DIAG_INFO instead of /proc/net/tcp.
Since that is user space I went ahead and sent the updated kernel patch
in a fresh thread.
rick
prev parent reply other threads:[~2007-09-11 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-10 23:13 [PATCH] include listenq max backlog in /proc/net/tcp and include in tcp_info Rick Jones
2007-09-11 0:39 ` Sridhar Samudrala
2007-09-11 6:09 ` Eric Dumazet
2007-09-11 6:54 ` Eric Dumazet
2007-09-11 17:00 ` Rick Jones
2007-09-11 17:15 ` Eric Dumazet
2007-09-11 17:35 ` Rick Jones
2007-09-11 17:46 ` Sridhar Samudrala
2007-09-11 18:10 ` Rick Jones [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=46E6DA03.2040602@hp.com \
--to=rick.jones2@hp.com \
--cc=dada1@cosmosbay.com \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
/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.