netdev - Re: [PATCH V6 00/20] net: ks8851: Unify KS8851 SPI and MLL drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 21 May 2020 15:11:37 +0200
From:   Marek Vasut <marex@...x.de>
To:     David Miller <davem@...emloft.net>, andrew@...n.ch
Cc:     lukas@...ner.de, netdev@...r.kernel.org, ynezz@...e.cz,
        yuehaibing@...wei.com
Subject: Re: [PATCH V6 00/20] net: ks8851: Unify KS8851 SPI and MLL drivers

On 5/17/20 9:30 PM, David Miller wrote:
> From: Andrew Lunn <andrew@...n.ch>
> Date: Sun, 17 May 2020 21:16:35 +0200
> 
>>> Nevertheless I was going to repeat the performance measurements on a
>>> recent kernel but haven't gotten around to that yet because the
>>> measurements need to be performed with CONFIG_PREEMPT_RT_FULL to
>>> be reliable (a vanilla kernel is too jittery), so I have to create
>>> a new branch with RT patches on the test machine, which is fairly
>>> involved and time consuming.
>>
>> I assume you will then mainline the changes, so you don't need to do
>> it again? That is the problem with doing development work on a dead
>> kernel.
> 
> I think the limitation is outside of his control as not all of the RT
> patches are in mainline yet.

So how shall we proceed here?

Some basic measurement results are here, for the reference [1].

[1] https://www.spinics.net/lists/netdev/msg643099.html