From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Fan Du <fan.du@windriver.com>
Cc: davem@davemloft.net, nicolas.dichtel@6wind.com,
yoshfuji@linux-ipv6.org, jmorris@namei.org,
steffen.klassert@secunet.com, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next V2] net: split rt_genid for ipv4 and ipv6
Date: Tue, 23 Jul 2013 04:04:37 +0200 [thread overview]
Message-ID: <20130723020437.GC30719@order.stressinduktion.org> (raw)
In-Reply-To: <1374543420-12657-1-git-send-email-fan.du@windriver.com>
On Tue, Jul 23, 2013 at 09:37:00AM +0800, Fan Du wrote:
> Current net name space has only one genid for both IPv4 and IPv6, it has below drawbacks:
>
> - Add/delete an IPv4 address will invalidate all IPv6 routing table entries.
> - Insert/remove XFRM policy will also invalidate both IPv4/IPv6 routing table entries
> even when the policy is only applied for one address family.
>
> Thus, this patch attempt to split one genid for two to cater for IPv4 and IPv6 separately
> in a fine granularity.
For me the approach seems reasonable. We should double-check if this
does not affect v4mapped af_inet6 sockets in any way. I could help to
do the review if there is an agreement that the split is desirable.
Thanks,
Hannes
next prev parent reply other threads:[~2013-07-23 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 1:37 [RFC PATCH net-next V2] net: split rt_genid for ipv4 and ipv6 Fan Du
2013-07-23 2:04 ` Hannes Frederic Sowa [this message]
2013-07-24 8:12 ` Fan Du
2013-07-23 21:51 ` Nicolas Dichtel
2013-07-24 1:30 ` Fan Du
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=20130723020437.GC30719@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=davem@davemloft.net \
--cc=fan.du@windriver.com \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=steffen.klassert@secunet.com \
--cc=yoshfuji@linux-ipv6.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).