All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
Cc: "Linux Kernel Network Developers" <netdev@vger.kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Subject: Re: [net-next-2.6 PATCH v4 3/3] TCPCT part 1c: initial SYN exchange with SYNACK data
Date: Mon, 02 Nov 2009 18:04:06 +0100	[thread overview]
Message-ID: <4AEF1106.40403@gmail.com> (raw)
In-Reply-To: <4AEF0603.7060502@gmail.com>

William Allen Simpson a écrit :

> It will be, when we have running code, as I'm loath to publish until I'm
> certain it *can* be implemented.

This is why RFC is better before coding. To avoid wasting time on experiments
that have a fatal flaw. Once included in an official kernel, we wont be able
to change some parameters very easily (think about 253 constant you use)

Or do you think only *you* can understand what's going on, and we should
just trust you ?

> 
> I've something like 40 RFCs published over the years.

I believe I know who you are, Mr William Allen Simpson, you dont need to
repeat how much work you did in the past. This is a bit annoying.

Some patches need 6-12 months of polishing before inclusion, there is nothing
wrong about it. It only depends on your cooperation and patience.

And yes, even if a patch comes from Linus Torvald himself, I can talk if
it does not please me.

SYNFLOOD problem is more than 13 years old, I am quite surprised its becoming
so urgent we should accept your patches "as is".


May I suggest to switch to normal mode, ie you prepare a next round of
patches, you submit them, we review them, [repeat 0-N time(s)], we Ack them ?


  reply	other threads:[~2009-11-02 17:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 12:11 [net-next-2.6 v4 0/4] TCPCT part1: cookie option exchange William Allen Simpson
2009-10-27 12:15 ` [net-next-2.6 PATCH v4 1/3] TCPCT part 1a: add request_values parameter for sending SYNACK William Allen Simpson
2009-11-01 19:13   ` Eric Dumazet
2009-10-27 12:18 ` [net-next-2.6 PATCH v4 2/3] TCPCT part 1b: sysctl_tcp_cookie_size, socket option TCP_COOKIE_TRANSACTIONS, functions William Allen Simpson
2009-11-01 19:13   ` Eric Dumazet
2009-11-02 10:45     ` William Allen Simpson
2009-11-02 10:51       ` David Miller
2009-11-02 17:54         ` William Allen Simpson
2009-10-27 12:29 ` [net-next-2.6 PATCH v4 3/3] TCPCT part 1c: initial SYN exchange with SYNACK data William Allen Simpson
2009-10-28 14:17   ` Eric Dumazet
2009-10-28 17:14     ` William Allen Simpson
2009-11-01 19:19   ` Eric Dumazet
2009-11-02 12:25     ` William Allen Simpson
2009-11-02 12:57       ` Ilpo Järvinen
2009-11-02 16:17         ` William Allen Simpson
2009-11-02 17:04           ` Eric Dumazet [this message]
2009-11-02 20:38             ` William Allen Simpson
2009-11-02 13:31       ` Eric Dumazet
2009-11-02 17:00       ` Joe Perches
2009-11-02 17:50         ` William Allen Simpson
2009-11-02 18:10   ` William Allen Simpson
2009-11-02 18:16     ` Joe Perches
2009-11-02 20:15       ` William Allen Simpson
2009-11-03  5:14         ` David 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=4AEF1106.40403@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=netdev@vger.kernel.org \
    --cc=william.allen.simpson@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.