netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hannes@stressinduktion.org
Cc: netdev@vger.kernel.org, hideaki@yoshifuji.org, kafai@fb.com,
	cwang@twopensource.com
Subject: Re: [PATCH v2 net-next 0/5] ipv6: cleanup after rt6_genid removal
Date: Tue, 07 Oct 2014 00:03:37 -0400 (EDT)	[thread overview]
Message-ID: <20141007.000337.1923110318110453432.davem@davemloft.net> (raw)
In-Reply-To: <cover.1412618014.git.hannes@stressinduktion.org>

From: Hannes Frederic Sowa <hannes@stressinduktion.org>
Date: Mon,  6 Oct 2014 19:58:33 +0200

> Leftover patches after rt6_genid removal after 705f1c869d577c ("ipv6:
> remove rt6i_genid").
> 
> Major two changes are:
> * keep fib6_sernum per namespace to reduce number of flushes in case
>   system has high number of namespaces
> * make fn_sernum updates cheaper
> 
> v2: Incorporated feedback from Cong Wang, thanks a lot!

Series applied, thanks.

      parent reply	other threads:[~2014-10-07  4:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06 17:58 [PATCH v2 net-next 0/5] ipv6: cleanup after rt6_genid removal Hannes Frederic Sowa
2014-10-06 17:58 ` [PATCH v2 net-next 1/5] ipv6: minor fib6 cleanups like type safety, bool conversion, inline removal Hannes Frederic Sowa
2014-10-06 17:58 ` [PATCH v2 net-next 2/5] ipv6: make rt_sernum atomic and serial number fields ordinary ints Hannes Frederic Sowa
2014-10-06 17:58 ` [PATCH v2 net-next 3/5] ipv6: only generate one new serial number per fib mutation Hannes Frederic Sowa
2014-10-06 17:58 ` [PATCH v2 net-next 4/5] ipv6: make fib6 serial number per namespace Hannes Frederic Sowa
2014-10-06 17:58 ` [PATCH v2 net-next 5/5] ipv6: don't walk node's leaf during serial number update Hannes Frederic Sowa
2014-10-07  4:03 ` David Miller [this message]

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=20141007.000337.1923110318110453432.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=cwang@twopensource.com \
    --cc=hannes@stressinduktion.org \
    --cc=hideaki@yoshifuji.org \
    --cc=kafai@fb.com \
    --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).