netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: [PATCH 0/7] Ipv6 TCP timewait recycling support
Date: Thu, 02 Dec 2010 12:41:58 -0800 (PST)	[thread overview]
Message-ID: <20101202.124158.71109616.davem@davemloft.net> (raw)


First we start with two simple cleanups, un-typedef'ification
and a comment fixup.

Then we add the infrastructure to allow the tcp_minisocks.c
timewait recycling code able to be generic and use various
->ops

Sadly, the ipv6 timewait ops are used even for v4-mapped
addresses so we need a special check in the ipv6 timewait
getpeer implementation.  This is similar to the situation
we have in tcp_v6_hash().

Doing these changes also pointed out that our listening socket
incoming connection policy in the non-syncookies case as
being handled differently for ipv4 vs. ipv6.  This has been
rectified.  The issue is that for ipv4 we were reserving the
final 1/4 of the backlog queue to validated destinations.

In the final patch we throw the switch and implement the two
getpeer operations for ipv6, which fully enables timewait
recyling for ipv6.

                 reply	other threads:[~2010-12-02 20:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20101202.124158.71109616.davem@davemloft.net \
    --to=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).