From: David Ahern
Date: Sun, 9 Dec 2018 20:29:04 -0700
> If this goes in can it target net-next first? Some soak time there
> will help show if there are any side effects before propagating to
> stable releases.
Ok.
Maciej please resubmit this specifically targetting net-next.
Thank you.
On 12/7/18 11:24 PM, David Miller wrote:
> From: Maciej Żenczykowski
> Date: Fri, 7 Dec 2018 16:46:36 -0800
>
>>> This doesn't apply to the current net tree.
>>>
>>> Also "net-udp: " is a weird subsystem prefix, just use "udp: ".
>>>
>>> Thank you.
>>
>> Interesting... this patch was on top of ne
From: Maciej Żenczykowski
Date: Fri, 7 Dec 2018 16:46:36 -0800
>> This doesn't apply to the current net tree.
>>
>> Also "net-udp: " is a weird subsystem prefix, just use "udp: ".
>>
>> Thank you.
>
> Interesting... this patch was on top of net-next/master, and it still
> rebases cleanly on curr
> This doesn't apply to the current net tree.
>
> Also "net-udp: " is a weird subsystem prefix, just use "udp: ".
>
> Thank you.
Interesting... this patch was on top of net-next/master, and it still
rebases cleanly on current net-next/master.
Would you like it on net/master instead? It indeed do
From: Maciej Żenczykowski
Date: Wed, 5 Dec 2018 12:59:17 -0800
> From: Maciej Żenczykowski
>
> During udp socket lookup cpu match should be lowest priority,
> hence it should increase score by only 1.
>
> The next priority is delivering v4 to v4 sockets, and v6 to v6 sockets.
> The v6 code pa
From: Maciej Żenczykowski
During udp socket lookup cpu match should be lowest priority,
hence it should increase score by only 1.
The next priority is delivering v4 to v4 sockets, and v6 to v6 sockets.
The v6 code path doesn't have to deal with this so it always gets
a score of '4'. The v4 code
