All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Omar Sandoval <osandov@osandov.com>
Cc: Omar Sandoval <osandov@fb.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Alexei Starovoitov <ast@fb.com>,
	Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [LSF/MM/BPF TOPIC] eBFP for block devices
Date: Mon, 2 May 2022 12:24:04 -0700	[thread overview]
Message-ID: <d78b3d02-99a5-7876-2a6a-8b5f52a05def@suse.de> (raw)
In-Reply-To: <YnAgJZUzDTTbAOXY@relinquished.localdomain>

On 5/2/22 11:17, Omar Sandoval wrote:
> On Mon, May 02, 2022 at 09:21:31AM -0700, Hannes Reinecke wrote:
>> Hi Omar,
>>
>> and another topic which came up during discussion yesterday:
>>
>> eBPF for block devices
>> It would be useful to enable eBPF for block devices, such that we could do
>> things like filtering bios on bio type, do error injection by modifying the
>> bio result etc.
>> This topic should be around how it could be implemented and what additional
>> use-cases could be supported.
>>
>> Cheers,
>>
>> Hannes
> 
> Do you want to try to coordinate a joint session with BPF, or were you
> planning on brainstorming what we need just in the IO track and tracking
> down the BPF folks offline?
> 
> +Alexei and Daniel

Coordinated session, please.
We need to get some common understandig of those things we're trying to 
do are properly eBPF-ish, and alse make the eBPF people aware of the 
issue we're facing.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare@suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer

  reply	other threads:[~2022-05-02 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-02 16:21 [LSF/MM/BPF TOPIC] eBFP for block devices Hannes Reinecke
2022-05-02 17:45 ` Gabriel Krisman Bertazi
2022-05-02 18:53   ` Martin K. Petersen
2022-05-02 20:28     ` Khazhy Kumykov
2022-05-02 20:34       ` Martin K. Petersen
2022-05-02 20:38         ` Hannes Reinecke
2022-05-02 20:47           ` Martin K. Petersen
2022-05-02 18:17 ` Omar Sandoval
2022-05-02 19:24   ` Hannes Reinecke [this message]
2023-01-29  3:20     ` Luis Chamberlain

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=d78b3d02-99a5-7876-2a6a-8b5f52a05def@suse.de \
    --to=hare@suse.de \
    --cc=ast@fb.com \
    --cc=daniel@iogearbox.net \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.com \
    --cc=osandov@osandov.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.