From: Ed Wildgoose <lists@wildgooses.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] TCP window based shaping
Date: Wed, 16 Feb 2005 14:52:31 +0000 [thread overview]
Message-ID: <42135E2F.9080908@wildgooses.com> (raw)
In-Reply-To: <42095013.8030600@wildgooses.com>
> Do you have to do do it differently for servers that do sacks, or do
> they still react to DUPs ?
Can someone provide a link to a table which lists tcp "implementations"
by OS? At the very least it would be interesting to know what features
and tcp implementations are used by WinXP, Win2K, Linux 2.4, Linux 2.6
and if possible also what Win98, ME and various BSD/Solaris
implementations use, although for my purposes I care less about these.
It's really hard to find out whether for example, SACK is implemented in
WinXP tcp...? I'm not even sure what changed between linux 2.4 and 2.6?
Thanks for any pointers
Ed W
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2005-02-16 14:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 23:49 [LARTC] TCP window based shaping Ed Wildgoose
2005-02-08 23:57 ` David Boreham
2005-02-09 1:59 ` Andy Furniss
2005-02-09 11:34 ` marco ghidinelli
2005-02-09 22:38 ` Andy Furniss
2005-02-11 2:57 ` Ed Wildgoose
2005-02-11 11:05 ` marco ghidinelli
2005-02-11 18:18 ` Ed Wildgoose
2005-02-11 23:45 ` Ed Wildgoose
2005-02-12 2:16 ` Andy Furniss
2005-02-12 13:19 ` Andy Furniss
2005-02-13 0:46 ` Ed Wildgoose
2005-02-14 0:27 ` marco ghidinelli
2005-02-14 0:38 ` marco ghidinelli
2005-02-15 22:33 ` Andy Furniss
2005-02-15 22:54 ` Andy Furniss
2005-02-16 14:52 ` Ed Wildgoose [this message]
2005-02-17 3:45 ` gypsy
2005-02-17 14:09 ` Ed Wildgoose
2005-03-12 10:10 ` Ow Mun Heng
2005-03-15 15:24 ` Ed Wildgoose
2005-03-16 7:46 ` Ow Mun Heng
2005-07-09 4:01 ` Don Cohen
2005-07-10 19:55 ` Andy Furniss
2005-07-12 1:50 ` TAKANO Ryousei
2005-07-12 8:46 ` Andy Furniss
2005-07-12 13:44 ` TAKANO Ryousei
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=42135E2F.9080908@wildgooses.com \
--to=lists@wildgooses.com \
--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.