From: Eric Dumazet <eric.dumazet@gmail.com>
To: Cyrus Sh <sirus.shahini@gmail.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
davem@davemloft.net
Cc: shiraz.saleem@intel.com, jgg@ziepe.ca, arnd@arndb.de,
netdev@vger.kernel.org, sirus@cs.utah.edu
Subject: Re: [PATCH] Clock-independent TCP ISN generation
Date: Tue, 3 Sep 2019 18:16:10 +0200 [thread overview]
Message-ID: <db9ad0f0-9aa8-4002-60e3-57124ef619ba@gmail.com> (raw)
In-Reply-To: <4ffba048-a46c-41da-ce67-e5dbac1de5a7@gmail.com>
On 9/3/19 6:12 PM, Cyrus Sh wrote:
>
>
> On 9/3/19 9:59 AM, Eric Dumazet wrote:
>
>> You could add a random delay to all SYN packets, if you believe your host has clock skews.
>
> And by the way adding delays has its own performance penalties.
>
You understand your patch has been rejected, right ?
You will have to convince people at IETF and get a proper RFC before
I even look at the idea.
BTW, sending a patch only dealing with IPv4 is also not a good thing.
next prev parent reply other threads:[~2019-09-03 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 5:06 [PATCH] Clock-independent TCP ISN generation Cyrus Sh
2019-09-03 7:41 ` Eric Dumazet
2019-09-03 15:39 ` Cyrus Sh
2019-09-03 15:59 ` Eric Dumazet
2019-09-03 16:06 ` Cyrus Sh
2019-09-03 16:17 ` Eric Dumazet
2019-09-03 16:27 ` Cyrus Sh
2019-09-03 16:42 ` Eric Dumazet
2019-09-03 22:45 ` David Miller
2019-09-04 0:45 ` Cyrus Sh
2019-09-03 22:43 ` David Miller
2019-09-03 16:12 ` Cyrus Sh
2019-09-03 16:16 ` Eric Dumazet [this message]
2019-09-03 7:45 ` kbuild test robot
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=db9ad0f0-9aa8-4002-60e3-57124ef619ba@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=jgg@ziepe.ca \
--cc=netdev@vger.kernel.org \
--cc=shiraz.saleem@intel.com \
--cc=sirus.shahini@gmail.com \
--cc=sirus@cs.utah.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).