From: Kenny Ho <y2kenny@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: bpf <bpf@vger.kernel.org>
Subject: Re: bpf helper functions from kernel module
Date: Fri, 23 Apr 2021 09:41:57 -0400 [thread overview]
Message-ID: <CAOWid-d956uyPv02UAgu2+pxk=ijPNodnV2FOki-=fkPycWkwQ@mail.gmail.com> (raw)
In-Reply-To: <87czumfexp.fsf@toke.dk>
On Thu, Apr 22, 2021 at 12:43 PM Toke Høiland-Jørgensen <toke@redhat.com> wrote:
>
> The support for calling kernel functions directly (AKA "unstable
> helpers") will likely be the way this will be achievable. See the
> comment in brackets half-way down in the description here:
>
> https://lore.kernel.org/bpf/20210325015142.1544736-1-kafai@fb.com/
Oh this is very cool, I will look into it. Thanks for the pointer.
Regards,
Kenny
prev parent reply other threads:[~2021-04-23 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 15:43 bpf helper functions from kernel module Kenny Ho
2021-04-22 16:43 ` Toke Høiland-Jørgensen
2021-04-23 13:41 ` Kenny Ho [this message]
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='CAOWid-d956uyPv02UAgu2+pxk=ijPNodnV2FOki-=fkPycWkwQ@mail.gmail.com' \
--to=y2kenny@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=toke@redhat.com \
/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).