netdev - Re: [PATCH net-next 01/12] net: homa: define user-visible API for Homa

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]

Message-ID: <20241108143208.2a08d972@hermes.local>
Date: Fri, 8 Nov 2024 14:32:08 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Edward Cree <ecree.xilinx@...il.com>
Cc: John Ousterhout <ouster@...stanford.edu>, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 01/12] net: homa: define user-visible API for
 Homa

On Fri, 8 Nov 2024 22:02:27 +0000
Edward Cree <ecree.xilinx@...il.com> wrote:

> > Do you know of other low-level kernel-call wrappers in
> > Linux that are analogous to these? If so, how are they handled?  
> 
> The closest analogy that comes to mind is the bpf system call and libbpf.
> libbpf lives in the tools/lib/bpf/ directory of the kernel tree, but is
>  often packaged and distributed independently[2] of the kernel package.
> If there is a reason to tie the maintenance of your wrappers to the
>  kernel project/git repo then this can be suitable.

liburing for ioring calls is a better example.
There are lots of versioning issues in any API. It took several years
for BPF to get to run anywhere status. Hopefully, you can learn from
those problems.