From: Paolo Abeni
Date: Fri, 07 Dec 2018 21:29:20 +0100
> Are you building with CONFIG_IPV6=m ?
I always build allmodconfig
Hi,
On Thu, 2018-12-06 at 22:28 -0800, David Miller wrote:
> From: David Miller
> Date: Thu, 06 Dec 2018 22:24:09 -0800 (PST)
>
> > Series applied, thanks!
>
> Erm... actually reverted. Please fix these build failures:
oops ...
I'm sorry for the late reply. I'm travelling and I will not able
From: David Miller
Date: Thu, 06 Dec 2018 22:24:09 -0800 (PST)
> Series applied, thanks!
Erm... actually reverted. Please fix these build failures:
ld: net/ipv6/ip6_offload.o: in function `ipv6_gro_receive':
ip6_offload.c:(.text+0xda2): undefined reference to `udp6_gro_receive'
ld: ip6_offload
From: Paolo Abeni
Date: Wed, 5 Dec 2018 19:13:38 +0100
> The spectre v2 counter-measures, aka retpolines, are a source of measurable
> overhead[1]. We can partially address that when the function pointer refers to
> a builtin symbol resorting to a list of tests vs well-known builtin function
>
From: Paolo Abeni
Date: Wed, 5 Dec 2018 19:13:38 +0100
...
> This may lead to some uglification around the indirect calls. In netconf 2018
> Eric Dumazet described a technique to hide the most relevant part of the
> needed
> boilerplate with some macro help.
>
> This series is a [re-]implemen
The spectre v2 counter-measures, aka retpolines, are a source of measurable
overhead[1]. We can partially address that when the function pointer refers to
a builtin symbol resorting to a list of tests vs well-known builtin function and
direct calls.
Experimental results show that replacing a singl
