From: "David S. Miller" <davem@redhat.com>
To: spy9599@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Few comments on TCP implementation
Date: Fri, 24 May 2002 14:20:09 -0700 (PDT) [thread overview]
Message-ID: <20020524.142009.51764018.davem@redhat.com> (raw)
In-Reply-To: <20020524213011.50807.qmail@web14808.mail.yahoo.com>
From: Yogesh Swami <spy9599@yahoo.com>
Date: Fri, 24 May 2002 14:30:11 -0700 (PDT)
c) There are numerous heuristics at work with no RFC
counterparts (rate halving etc etc). To have the best
performance its probably best to stick with RFCs, or
if there is a compelling need to have these heuristics
then they should be brought to the IETF first.
Implementing something based on someone's random
publications is not a good idea for an operating as
pervasive as Linux.
Wrong. Half of the RFCs have flaws, and if we just would "stick to
RFCs" we'd have a lot of problems. Most of things Linux does
different are just fixes for these errors in the RFCs.
next prev parent reply other threads:[~2002-05-24 21:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 21:30 Yogesh Swami
2002-05-24 21:20 ` David S. Miller [this message]
2002-05-24 21:23 ` David S. Miller
2002-05-24 22:51 ` kuznet
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=20020524.142009.51764018.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spy9599@yahoo.com \
/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®