From: William Allen Simpson <william.allen.simpson@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] TCPCT+1: initial SYN exchange with SYNACK data
Date: Mon, 05 Oct 2009 03:58:12 -0400 [thread overview]
Message-ID: <4AC9A714.7060903@gmail.com> (raw)
In-Reply-To: <20091005.002719.146534039.davem@davemloft.net>
David Miller wrote:
> From: William Allen Simpson <william.allen.simpson@gmail.com>
> Date: Sat, 03 Oct 2009 14:33:41 -0400
>
>> @@ -406,6 +454,32 @@ struct tcp_sock {
> ...
>> + struct tcp_s_data_payload *s_data_payload;
> ...
>> + struct tcp_cookie_pair *cookie_pair;
> ...
>> + u16 s_data_desired; /* bytes */
> ...
>> + u8 cookie_desired; /* bytes */
>> + u8 s_data_in:1,
>> + s_data_out:1,
>> + cookie_in_always:1,
>> + cookie_out_never:1;
>
> struct tcp_sock is already WAY TOO BIG on 64-bit systems, adding 20
> more bytes to it for some odd-ball feature is not something I'm
> willing to do, sorry.
>
I see we're cross-posting at the same time.... Since in your previous
review (last year) this issue was not mentioned, is there some other
data organization that you would suggest?
http://article.gmane.org/gmane.linux.network/102779
"This looks mostly fine to me. I would even advocate not using a config
option for this."
Perhaps you would prefer this as a config option after all?
As for "odd-ball feature", of course this is the initial pass on a much
larger project....
next prev parent reply other threads:[~2009-10-05 7:58 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 [this message]
2009-10-05 8:06 ` David Miller
2009-10-05 8:23 ` William Allen Simpson
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=4AC9A714.7060903@gmail.com \
--to=william.allen.simpson@gmail.com \
--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 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.