Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Arkadiusz Miśkiewicz" <a.miskiewicz@gmail.com>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH] inet:
Date: Sat, 26 Nov 2011 23:16:30 +0100	[thread overview]
Message-ID: <1322345790.10212.23.camel@edumazet-laptop> (raw)
In-Reply-To: <1322345624.10212.21.camel@edumazet-laptop>

Le samedi 26 novembre 2011 à 23:13 +0100, Eric Dumazet a écrit :
> Now inetpeer is the place where we cache redirect information for ipv4
> destinations, we must be able to invalidate informations when a route is
> added/removed on host.
> 
> As inetpeer is not yet namespace aware, this patch adds a shared
> redirect_genid, and a per inetpeer redirect_genid. This might be changed
> later if inetpeer becomes ns aware.
> 
> Cache information for one inerpeer is valid as long as its
> redirect_genid has the same value than global redirect_genid.
> 
> Reported-by: Arkadiusz Miśkiewicz <a.miskiewicz@gmail.com>
> Tested-by: Arkadiusz Miśkiewicz <a.miskiewicz@gmail.com>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
> ---

Arg, patch title was not complete, it could be :

[PATCH] inet: add a redirect generation id in inetpeer

Sorry :(

  reply	other threads:[~2011-11-26 22:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-23 18:10 cache forver in 3.2.0-rc2-00400-g866d43c ? Arkadiusz Miśkiewicz
2011-11-23 18:22 ` Eric Dumazet
2011-11-23 18:31   ` Arkadiusz Miśkiewicz
2011-11-23 18:37     ` Eric Dumazet
2011-11-23 19:44       ` Eric Dumazet
2011-11-23 20:35         ` Arkadiusz Miśkiewicz
2011-11-25 17:53           ` Arkadiusz Miśkiewicz
2011-11-26 22:10             ` Eric Dumazet
2011-11-26 22:13             ` [PATCH] inet: Eric Dumazet
2011-11-26 22:16               ` Eric Dumazet [this message]
2011-11-27  0:17                 ` David Miller

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=1322345790.10212.23.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=a.miskiewicz@gmail.com \
    --cc=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