From: kuznet@ms2.inr.ac.ru
To: ak@suse.de (Andi Kleen)
Cc: ak@suse.de, linux-kernel@vger.rutgers.edu
Subject: Re: Missing ACKs with Linux 2.2/2.4?
Date: Sun, 12 Nov 2000 18:59:27 +0300 (MSK) [thread overview]
Message-ID: <200011121600.TAA17075@ms2.inr.ac.ru> (raw)
In-Reply-To: <20001112163538.A10339@gruyere.muc.suse.de> from "Andi Kleen" at Nov 12, 0 04:35:38 pm
Hello!
> The probability of just exactly the zero packet hitting you is very small.
... long laughter ...
Andi, I see you are not very strong in methematics. 8)
Timestamp is not a random number, so that probability of PAWS failure
does not depend on restricting it at all. The only thing which can help
to reduce probability is dropping all tpacket with ts_val==0
or shutting down your machine while time of your peers passes through zero. 8)
BTW I looked to netbsd and certainly did not find any signs of said by you.
They drop packet with ts_val before ts_recent, even if ts_val is zero.
They really have bug, considering zero value of ts_recent as invalid one.
This make PAWS something absolutely useless. 8)
Alexey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next parent reply other threads:[~2000-11-12 16:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20001112163538.A10339@gruyere.muc.suse.de>
2000-11-12 15:59 ` kuznet [this message]
2000-11-17 5:37 Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2000-11-17 5:36 Bernd Eckenfels
2000-11-11 19:26 Bernd Eckenfels
2000-11-11 22:27 ` David S. Miller
2000-11-12 13:30 ` Andi Kleen
2000-11-12 14:26 ` kuznet
2000-11-09 19:36 Ben Mansell
2000-11-10 0:20 ` David S. Miller
2000-11-10 10:13 ` Ben Mansell
2000-11-10 10:12 ` David S. Miller
2000-11-10 11:49 ` Ben Mansell
2000-11-10 11:46 ` David S. Miller
2000-11-10 14:54 ` Ben Mansell
2000-11-10 11:50 ` David S. Miller
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=200011121600.TAA17075@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=ak@suse.de \
--cc=linux-kernel@vger.rutgers.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
all inboxes | Powered by JetHome®