From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: [PATCH 0/3] IPv6 inetpeer support
Date: Mon, 29 Nov 2010 13:43:57 -0800 (PST) [thread overview]
Message-ID: <20101129.134357.102563313.davem@davemloft.net> (raw)
Here is the beginning of some refactoring I've been working on.
It's a respin of my older inet-peer ipv6 support patch plus the
beginnings of what's necessary to support TCP time-wait recycling
in ipv6 too.
I also intend to investigate more deeply putting metrics into
the inet-peer cache, but nothing about that is in this series
as that is still a not so clear-and-dry issue.
Supporting the same set of TCP features in both ipv4 and ipv6
is, on the other hand, less controversial so I think we should
do the ipv6 inet-peer thing no matter what.
reply other threads:[~2010-11-29 21:43 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=20101129.134357.102563313.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).