From: Stephen Hemminger <shemminger@vyatta.com>
To: Lisong Xu <lisongxu2@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: TCP Congestion Control Algorithms
Date: Mon, 31 Aug 2009 15:07:31 -0700 [thread overview]
Message-ID: <20090831150731.28c36081@nehalam> (raw)
In-Reply-To: <a45e9b40908311410m486a60fel6a81c334732de358@mail.gmail.com>
On Mon, 31 Aug 2009 16:10:59 -0500
Lisong Xu <lisongxu2@gmail.com> wrote:
> Hello,
>
> Since there are multiple different TCP congestion control algorithms
> available in Linux, a Linux server may use any of them.
>
> Is it possible for a regular user to find out the exact TCP congestion
> control algorithm used by a Linux server? For example, if I am
> downloading a file from a remote Linux server using a TCP flow, can I
> find out whether this flow is a TCP/CUBIC flow, or TCP/Newreno, or
> some other TCP protocol?
>
No. you might be able to some nmap style guessing, but no remote
API. You can see locally on the server through /proc/sys/net
next prev parent reply other threads:[~2009-08-31 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a45e9b40908311408l15d68088i459d6a1000cbca07@mail.gmail.com>
2009-08-31 21:10 ` TCP Congestion Control Algorithms Lisong Xu
2009-08-31 22:07 ` Stephen Hemminger [this message]
2009-09-01 0:37 ` Lisong Xu
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=20090831150731.28c36081@nehalam \
--to=shemminger@vyatta.com \
--cc=lisongxu2@gmail.com \
--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).