BPF List
 help / color / mirror / Atom feed
From: sdf@google.com
To: Gavin Ray <ray.gavin97@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: Applicability of BPF as a general-purpose programming language/runtime platform?
Date: Sat, 12 Nov 2022 18:02:02 -0800	[thread overview]
Message-ID: <Y3BQGgcCMaSptEFJ@google.com> (raw)
In-Reply-To: <CAFtvWZN937H9D2mKTXevpH8SvrZ_pSNGmAwT5vOR3CZoCzipZQ@mail.gmail.com>

On 11/12, Gavin Ray wrote:
> Hi all,

> Apologies if questions/non-patch content aren't allowed on the mailing  
> list,
> I've not used the Linux kernel lists before so not certain of the
> rules/etiquette.

> I watched the talk from LPC, "The journey of BPF from restricted C  
> language
> towards extended and safe C" recently and many of the properties seemed
> desirable. Particularly things like bounds-checking and verifiable  
> locking.

> Is it possible to use BPF as a general-purpose language for writing  
> software?
> If not, is it planned for the future? (Or maybe it's not technically  
> possible)

I'm aware of at least the following:

https://github.com/iovisor/ubpf
https://github.com/qmonnet/rbpf

These projects are developed outside of the kernel and provide a
more-or-less-general-purpose BPF runtime.

> Would be pretty neat, in my opinion.
> Thanks and best regards,
> --
> Gavin

> (P.S. Will I receive replies to this message?)

      reply	other threads:[~2022-11-13  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12 19:46 Applicability of BPF as a general-purpose programming language/runtime platform? Gavin Ray
2022-11-13  2:02 ` sdf [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=Y3BQGgcCMaSptEFJ@google.com \
    --to=sdf@google.com \
    --cc=bpf@vger.kernel.org \
    --cc=ray.gavin97@gmail.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