From: George Michaelson <ggm@apnic.net>
To: 9fans@cse.psu.edu
Subject: [9fans] trouble down t'labs
Date: Fri, 24 Oct 2003 14:32:05 +1000 [thread overview]
Message-ID: <20031024143205.0c5626a3.ggm@apnic.net> (raw)
In-Reply-To: <20031023021628.GH834@cassie.foobarbaz.net>
AT&T have admitted to severe SPAM related slowdowns. It might be that the data
congestion along the path is causing so much packetloss, crypted and other loss-
intolerant paths are not working well.
how much of 9 protocol is over IP or UDP rather than TCP? I suppose even if TCP,
it could score massive delay as the windowsize kept down due to fragloss.
Only a hypotenuse. Somebody more in-the-know can kybosh it.
-George
next prev parent reply other threads:[~2003-10-24 4:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 15:43 [9fans] venti+fossil, the boot process, and 48-bit lba Christopher Nielsen
2003-10-22 15:57 ` Charles Forsyth
2003-10-22 17:10 ` Christopher Nielsen
2003-10-22 17:29 ` Christopher Nielsen
2003-10-22 17:58 ` Charles Forsyth
2003-10-22 18:06 ` Russ Cox
2003-10-22 20:07 ` vdharani
2003-10-22 19:59 ` Christopher Nielsen
2003-10-23 2:16 ` Christopher Nielsen
2003-10-24 4:32 ` George Michaelson [this message]
2003-10-27 7:48 ` Christopher Nielsen
2003-10-22 16:08 ` ron minnich
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=20031024143205.0c5626a3.ggm@apnic.net \
--to=ggm@apnic.net \
--cc=9fans@cse.psu.edu \
/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).