From: Andi Kleen <ak@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: ecki@lina.inka.de, linux-kernel@vger.kernel.org
Subject: Re: Missing ACKs with Linux 2.2/2.4?
Date: Sun, 12 Nov 2000 14:30:47 +0100 [thread overview]
Message-ID: <20001112143047.A9227@gruyere.muc.suse.de> (raw)
In-Reply-To: <E13ugIb-0004jA-00@calista.inka.de> <200011112227.OAA02548@pizda.ninka.net>
In-Reply-To: <200011112227.OAA02548@pizda.ninka.net>; from davem@redhat.com on Sat, Nov 11, 2000 at 02:27:13PM -0800
On Sat, Nov 11, 2000 at 02:27:13PM -0800, David S. Miller wrote:
> From: Bernd Eckenfels <ecki@lina.inka.de>
> Date: Sat, 11 Nov 2000 20:26:49 +0100
>
> Or is timestamp 0 a legal value?
>
> It is legal.
NetBSD ignores 0 timestamps. Although that's a hack it is IMHO a reasonable one and
Linux should probably do it too. Even when the 0 is generated legitimately by wrapping
counters it is probably not a big problem to lose timestamps for such few packets.
-Andi
-
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 prev parent reply other threads:[~2000-11-12 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 19:26 Bernd Eckenfels
2000-11-11 22:27 ` David S. Miller
2000-11-12 13:30 ` Andi Kleen [this message]
2000-11-12 14:26 ` kuznet
-- strict thread matches above, loose matches on Subject: below --
2000-11-17 5:37 Bernd Eckenfels
2000-11-17 5:36 Bernd Eckenfels
[not found] <20001112163538.A10339@gruyere.muc.suse.de>
2000-11-12 15:59 ` 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=20001112143047.A9227@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=davem@redhat.com \
--cc=ecki@lina.inka.de \
--cc=linux-kernel@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 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®