From: Stephen Hemminger <stephen@networkplumber.org>
To: Edward Cree <ecree.xilinx@gmail.com>
Cc: John Ousterhout <ouster@cs.stanford.edu>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 01/12] net: homa: define user-visible API for Homa
Date: Fri, 8 Nov 2024 14:32:08 -0800 [thread overview]
Message-ID: <20241108143208.2a08d972@hermes.local> (raw)
In-Reply-To: <6467b078-4ee9-ecb2-6174-825c3a2d5007@gmail.com>
On Fri, 8 Nov 2024 22:02:27 +0000
Edward Cree <ecree.xilinx@gmail.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.
next prev parent reply other threads:[~2024-11-08 22:32 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 21:35 [PATCH net-next 00/12] Begin upstreaming Homa transport protocol John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 01/12] net: homa: define user-visible API for Homa John Ousterhout
2024-10-29 21:59 ` Andrew Lunn
2024-10-30 4:06 ` John Ousterhout
2024-10-30 12:41 ` Andrew Lunn
2024-11-01 17:47 ` John Ousterhout
2024-11-01 18:01 ` Andrew Lunn
2024-11-07 21:58 ` Edward Cree
2024-11-08 17:55 ` John Ousterhout
2024-11-08 22:02 ` Edward Cree
2024-11-08 22:32 ` Stephen Hemminger [this message]
2024-10-28 21:35 ` [PATCH net-next 02/12] net: homa: define Homa packet formats John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 03/12] net: homa: create shared Homa header files John Ousterhout
2024-10-29 6:47 ` kernel test robot
2024-11-02 19:39 ` John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 04/12] net: homa: create homa_pool.h and homa_pool.c John Ousterhout
2024-10-30 0:09 ` Andrew Lunn
2024-10-30 4:15 ` John Ousterhout
2024-10-30 12:54 ` Andrew Lunn
2024-10-30 15:48 ` John Ousterhout
2024-11-04 13:12 ` Przemek Kitszel
2024-11-04 23:57 ` John Ousterhout
[not found] ` <CAGXJAmyLsx9DPGdhZwPxn0wXjFAFV3dqjhFHpaBLtKZ1mtYBSQ@mail.gmail.com>
[not found] ` <16f2e9cc-9b5e-4325-b5c7-fe7fd72600a8@lunn.ch>
2024-10-30 20:13 ` John Ousterhout
2024-10-30 20:17 ` John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 05/12] net: homa: create homa_rpc.h and homa_rpc.c John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 06/12] net: homa: create homa_peer.h and homa_peer.c John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 07/12] net: homa: create homa_sock.h and homa_sock.c John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 08/12] net: homa: create homa_incoming.c John Ousterhout
2024-10-30 1:13 ` Andrew Lunn
2024-10-30 4:51 ` John Ousterhout
2024-10-30 13:06 ` Andrew Lunn
2024-10-30 15:49 ` John Ousterhout
2024-10-30 18:23 ` Eric Dumazet
2024-10-30 18:33 ` John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 09/12] net: homa: create homa_outgoing.c John Ousterhout
2024-10-30 0:42 ` Andrew Lunn
2024-10-30 4:30 ` John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 10/12] net: homa: create homa_timer.c John Ousterhout
2024-10-30 19:02 ` Eric Dumazet
2024-10-31 18:55 ` John Ousterhout
2024-10-28 21:35 ` [PATCH net-next 11/12] net: homa: create homa_plumbing.c homa_utils.c John Ousterhout
2024-10-30 1:03 ` Andrew Lunn
2024-10-28 21:35 ` [PATCH net-next 12/12] net: homa: create Makefile and Kconfig John Ousterhout
2024-10-29 14:00 ` kernel test robot
2024-10-29 14:21 ` kernel test robot
2024-10-29 18:42 ` kernel test robot
2024-10-30 1:09 ` kernel test robot
2024-11-03 0:11 ` John Ousterhout
-- strict thread matches above, loose matches on Subject: below --
2024-12-09 17:51 [PATCH net-next v3 00/12] Begin upstreaming Homa transport protocol John Ousterhout
2024-12-09 17:51 ` [PATCH net-next 01/12] net: homa: define user-visible API for Homa John Ousterhout
2024-12-09 17:54 ` John Ousterhout
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241108143208.2a08d972@hermes.local \
--to=stephen@networkplumber.org \
--cc=ecree.xilinx@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ouster@cs.stanford.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).