From: Martin KaFai Lau
Date: Fri, 28 Aug 2015 00:36:38 -0700
> On Mon, Aug 17, 2015 at 11:43:20AM +0200, Alexander Holler wrote:
>> That's why I vote to check out if it's possible/reasonable to backport this
>> series to the stable kernels.
> I have backported to 4.0.y without major issue, so pos
Am 28.08.2015 um 11:27 schrieb Alexander Holler:
Am 28.08.2015 um 09:36 schrieb Martin KaFai Lau:
On Mon, Aug 17, 2015 at 11:43:20AM +0200, Alexander Holler wrote:
That's why I vote to check out if it's possible/reasonable to
backport this
series to the stable kernels.
I have backported to 4.0
Am 28.08.2015 um 09:36 schrieb Martin KaFai Lau:
On Mon, Aug 17, 2015 at 11:43:20AM +0200, Alexander Holler wrote:
That's why I vote to check out if it's possible/reasonable to backport this
series to the stable kernels.
I have backported to 4.0.y without major issue, so possible.
Sure, as th
On Mon, Aug 17, 2015 at 11:43:20AM +0200, Alexander Holler wrote:
> That's why I vote to check out if it's possible/reasonable to backport this
> series to the stable kernels.
I have backported to 4.0.y without major issue, so possible.
I did try on 3.1x and gave up.
It is a lot of changes, so I
Am 15.08.2015 um 09:48 schrieb Alexander Holler:
Am 30.07.2015 um 13:57 schrieb Alexander Holler:
Am 29.07.2015 um 11:25 schrieb Alexander Holler:
Am 23.05.2015 um 05:55 schrieb Martin KaFai Lau:
To complete the discussion, that "annoying behaviour" is also a big
information leak.
Because r
Am 30.07.2015 um 13:57 schrieb Alexander Holler:
Am 29.07.2015 um 11:25 schrieb Alexander Holler:
Am 23.05.2015 um 05:55 schrieb Martin KaFai Lau:
This series is to avoid creating a RTF_CACHE route whenever we are
consulting
the fib6 tree with a new destination. Instead, only create RTF_CACHE
Am 29.07.2015 um 11:25 schrieb Alexander Holler:
Am 23.05.2015 um 05:55 schrieb Martin KaFai Lau:
This series is to avoid creating a RTF_CACHE route whenever we are
consulting
the fib6 tree with a new destination. Instead, only create RTF_CACHE
route
when we see a pmtu exception.
That even h
Am 23.05.2015 um 05:55 schrieb Martin KaFai Lau:
This series is to avoid creating a RTF_CACHE route whenever we are consulting
the fib6 tree with a new destination. Instead, only create RTF_CACHE route
when we see a pmtu exception.
That even helps on systems without an IPv6-connection to worl
On Tue, May 26, 2015 at 11:20:53PM +0200, Hannes Frederic Sowa wrote:
> I also went over the changes to the last version and such, albeit a bit
> late:
> Reviewed-by: Hannes Frederic Sowa
Thanks for your help and review, Hannes!
--Martin
--
To unsubscribe from this list: send the line "unsubscrib
On Mon, May 25, 2015, at 19:34, David Miller wrote:
> From: Martin KaFai Lau
> Date: Fri, 22 May 2015 20:55:55 -0700
>
> > This series is to avoid creating a RTF_CACHE route whenever we are
> > consulting
> > the fib6 tree with a new destination. Instead, only create RTF_CACHE route
> > when we
From: Martin KaFai Lau
Date: Fri, 22 May 2015 20:55:55 -0700
> This series is to avoid creating a RTF_CACHE route whenever we are consulting
> the fib6 tree with a new destination. Instead, only create RTF_CACHE route
> when we see a pmtu exception.
Looks great, nice work.
Series applied to ne
v4 -> v5:
- Patch 1 is new. Clean up the ipv6_select_ident() and ip6_fragment().
- Further simplify the newly added rt6_get_pcpu_route(). If there is a
'prev' after cmpxchg, return prev instead of the newly created percpu
clone.
v3 -> v4:
- Patch 8 is new. It keeps track of the DST_NOCACHE r
12 matches
Mail list logo
