archive mirror
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <>
To: Fan Du <>
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: <> (raw)
In-Reply-To: <>

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.



  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 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [RFC PATCH net-next V2] net: split rt_genid for ipv4 and ipv6' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).