From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to read the TCP congestion window (cwnd) on Linux?
Date: Mon, 02 May 2005 21:14:53 +0000 [thread overview]
Message-ID: <4276984D.7070004@trash.net> (raw)
In-Reply-To: <427661C9.4080507@iit.cnr.it>
Antonio Pinizzotto wrote:
>
> Hi everybody.
> Do you know about any way to read the TCP cwnd value (congestion window)
> on Linux?
>
> I have read that on Linux it is not possible to enable a socket option
> (to read to cwnd using the program trpt).
>
> Any way to read the cwnd would be good for me.
I already answered your question on the end2end list yesterday:
You can get cwnd through the TCP socket monitoring interface using the
"ss"-tool from iproute2 (http://developer.osdl.org/dev/iproute2) or by
getsockopt(TCP_INFO).
Regards
Patrick
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2005-05-02 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 17:22 [LARTC] How to read the TCP congestion window (cwnd) on Linux? Antonio Pinizzotto
2005-05-02 21:14 ` Patrick McHardy [this message]
2005-05-03 21:27 ` Stephen Hemminger
2005-05-04 7:54 ` Sorin S.
2005-05-04 16:17 ` Stephen Hemminger
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=4276984D.7070004@trash.net \
--to=kaber@trash.net \
--cc=lartc@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 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.