From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: fan.du@windriver.com, nicolas.dichtel@6wind.com,
yoshfuji@linux-ipv6.org, jmorris@namei.org,
steffen.klassert@secunet.com, paul@paul-moore.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4] net: split rt_genid for ipv4 and ipv6
Date: Wed, 31 Jul 2013 14:57:10 -0700 (PDT) [thread overview]
Message-ID: <20130731.145710.1507535169314670977.davem@davemloft.net> (raw)
In-Reply-To: <20130730070702.GG2490@order.stressinduktion.org>
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Tue, 30 Jul 2013 09:07:02 +0200
> On Tue, Jul 30, 2013 at 08:33:53AM +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.
>>
>> Signed-off-by: Fan Du <fan.du@windriver.com>
>
> Also this patch only applies with some fuzz, it addressed all my issues:
>
> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Applied, thanks.
next prev parent reply other threads:[~2013-07-31 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 0:33 [PATCH net-next v4] net: split rt_genid for ipv4 and ipv6 Fan Du
2013-07-30 7:07 ` Hannes Frederic Sowa
2013-07-31 21:57 ` David Miller [this message]
2013-08-01 0:33 ` 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=20130731.145710.1507535169314670977.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fan.du@windriver.com \
--cc=hannes@stressinduktion.org \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=paul@paul-moore.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).