From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] kernel updates
Date: Tue, 16 Jul 2002 15:49:54 -0400 [thread overview]
Message-ID: <0113a037afb5d6a94f6fb107a4fadb28@plan9.bell-labs.com> (raw)
I've copied a scad of changes onto the sources machine. In
particular
- I've hacked the hell out of TCP to get rid of
all the anomalies I could find.
> The problem LANL was having with throughput
dropping off drasticly with write size is gone.
> we no longer do lots of needless retransmissions
> IP CPU overhead is down (took out some high rollers)
- I've added SYN attack defenses. I used the low
state model rather than the SYN cookie one.
- a defense for NAPTHA DOS attacks from Dong Lin.
I don't think I've picked up any works in progress.
I still want to add scalable TCP windows but ran out
of time. I'll do it in a few weeks. It might help
with GB ethernet.
next reply other threads:[~2002-07-16 19:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-16 19:49 presotto [this message]
2002-07-17 8:58 ` Don
2002-07-16 20:14 dpx
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=0113a037afb5d6a94f6fb107a4fadb28@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.com \
--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).