Re: [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC.

From: Komuro <[email protected]>
Date: Sun, 14 Oct 2007 10:02:45 +0900

> Dear David
> 
> Actually, tcp_sk(sk)->snd_ssthresh is not initialized,
> if initial_ssthresh is 0.

Komuro, every single email I sent to you bounces with "user unknown",
I bet it is some spam filter or similar that doesn't like the
fact that I lack reverse DNS.

Can someone tell Komuro this side-band?  He also missed my
previous reply, which directed him to make his report on
[email protected] which is very important.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC.
    • From: Jeff Garzik <[email protected]>

• References:
  • RE: [PATCH] Simplify yenta code
    • From: Komuro <[email protected]>
  • [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC.
    • From: Komuro <[email protected]>
  • Re: [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC.
    • From: Komuro <[email protected]>

• Prev by Date: [PATCH] Update Jens Axboe's email in Documentation/*
• Next by Date: Re: x86: merge some trivially mergeable headers
• Previous by thread: Re: [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC.
• Next by thread: Re: [NOT VERY SAFE] [TCP]: Set initial_ssthresh default to zero in Cubic and BIC.
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]