From: David Miller <davem@davemloft.net>
To: therbert@google.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH] net: Provide SYN packet for passive connections
Date: Sun, 11 Mar 2012 21:14:24 -0700 (PDT) [thread overview]
Message-ID: <20120311.211424.996831768685832926.davem@davemloft.net> (raw)
In-Reply-To: <CA+mtBx_LqwUpe5Df3VPw-L=h-WUjr=fxh86rgNuYnMacNikuOA@mail.gmail.com>
From: Tom Herbert <therbert@google.com>
Date: Sun, 11 Mar 2012 21:08:38 -0700
> For inet_connection_sock I believe there are fields that would only be
> used for a listeners(e.g. icsk_accept_queue), and fields that would
> only be used for a real connection (e.g. icsk_retransmits). Would it
> be worth it to split these into a union?
Indeed, it might.
next prev parent reply other threads:[~2012-03-12 4:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 2:48 [PATCH] net: Provide SYN packet for passive connections Tom Herbert
2012-03-12 2:55 ` David Miller
2012-03-12 4:08 ` Tom Herbert
2012-03-12 4:14 ` David Miller [this message]
2012-03-13 4:01 ` Eric Dumazet
2012-03-13 5:56 ` David Miller
2012-03-12 3:10 ` Eric Dumazet
2012-03-12 3:18 ` Tom Herbert
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=20120311.211424.996831768685832926.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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;
as well as URLs for NNTP newsgroup(s).