From: William Allen Simpson <william.allen.simpson@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] TCPCT+1: initial SYN exchange with SYNACK data
Date: Mon, 05 Oct 2009 04:23:48 -0400 [thread overview]
Message-ID: <4AC9AD14.2060500@gmail.com> (raw)
In-Reply-To: <20091005.010630.214808506.davem@davemloft.net>
David Miller wrote:
> I'm looking at the patch more closely, and as I learn more
> things about your change, my position changes.
>
>> Perhaps you would prefer this as a config option after all?
>
> No, then nobody is going to deploy this thing (meaning it really will
> be useless), or everyone will and everyone will enable it and thus eat
> the space.
>
> It's bad either way.
>
> Store the data either somewhere else or in an extremely compact form.
>
More cross-posting, a good thing for responsiveness....
OK, no config option.
This will be widely deployed. Deployment in DNS root servers is
expected by December. It will be hammered with 600,000+ queries per
minute. Does that impact your design expectations?
Tomorrow, I'll send out a new patch with everything buried in a single
kref, the various tests will only be a trifle slower....
next prev parent reply other threads:[~2009-10-05 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 18:33 [PATCH] TCPCT+1: initial SYN exchange with SYNACK data William Allen Simpson
2009-10-05 7:27 ` David Miller
2009-10-05 7:58 ` William Allen Simpson
2009-10-05 8:06 ` David Miller
2009-10-05 8:23 ` William Allen Simpson [this message]
2009-10-05 8:50 ` David Miller
2009-10-05 9:22 ` Eric Dumazet
2009-10-05 8:11 ` William Allen Simpson
2009-10-05 8:45 ` David Miller
2009-10-05 17:42 ` William Allen Simpson
2009-10-05 7:45 ` William Allen Simpson
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=4AC9AD14.2060500@gmail.com \
--to=william.allen.simpson@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).