netdev - Re: [PATCH net-next 12/13] selftests: ncdevmem: Move ncdevmem under drivers/net

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHS8izNTgbf-654fB84Wiz1kgA4z5HoicDm_MuGS_72561AnuA@mail.gmail.com>
Date: Fri, 13 Sep 2024 08:38:47 -0700
From: Mina Almasry <almasrymina@...gle.com>
To: Stanislav Fomichev <sdf@...ichev.me>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com, 
	kuba@...nel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next 12/13] selftests: ncdevmem: Move ncdevmem under drivers/net

On Thu, Sep 12, 2024 at 10:13 AM Stanislav Fomichev <sdf@...ichev.me> wrote:
>
> This is where all the tests that depend on the HW functionality live in

Is this true? My impression is that selftests/net verifies core
functionality and drivers/net verifies more lower level driver
(specific?) functionality. There are tests in selftests/net that
depend on HW functionality, I think like bpf_offload.py.

devmem tcp in my mind is primarily a core functionality and a lot of
effort was put into making the driver bits of it as minimal as
possible. Is there a need to move it or is this preference?

-- 
Thanks,
Mina