[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20111126.191712.529707882787134808.davem@davemloft.net>
Date: Sat, 26 Nov 2011 19:17:12 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: a.miskiewicz@...il.com, netdev@...r.kernel.org
Subject: Re: [PATCH] inet:
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Sat, 26 Nov 2011 23:16:30 +0100
> 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@...il.com>
>> Tested-by: Arkadiusz Miśkiewicz <a.miskiewicz@...il.com>
>> Signed-off-by: Eric Dumazet <eric.dumazet@...il.com>
>> ---
>
> Arg, patch title was not complete, it could be :
>
> [PATCH] inet: add a redirect generation id in inetpeer
It happens :-) Applied, thanks Eric.
Powered by blists - more mailing lists