From: Luis Gerhorst <[email protected]>
To: [email protected]
Cc: [email protected], [email protected], [email protected],
[email protected]
Date: Fri, 06 Nov 2020 11:44:27 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
Hello Pavel,
I'm from a university and am searching for a project to work on in the
upcoming year. I am looking into allowing userspace to run multiple
system calls interleaved with application-specific logic using a single
context switch.
I noticed that you, Jens Axboe, and Carter Li discussed the possibility
of integrating eBPF into io_uring earlier this year [1, 2, 3]. Is there
any WIP on this topic?
If not I am considering to implement this. Besides the fact that AOT
eBPF is only supported for priviledged processes, are there any issues
you are aware of or reasons why this was not implemented yet?
Best,
Luis
[1] https://lore.kernel.org/io-uring/[email protected]/
[2] https://lore.kernel.org/io-uring/[email protected]/
[3] https://github.com/axboe/liburing/issues/58
next reply other threads:[~2020-11-06 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 10:44 Luis Gerhorst [this message]
2020-11-06 10:50 ` Integrating eBPF into io-uring linux-kernel
2020-11-06 14:34 ` Pavel Begunkov
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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