From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Hannes Reinecke <hare@suse.de>
Cc: Omar Sandoval <osandov@fb.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"Khazhismel Kumykov" <khazhy@google.com>
Subject: Re: [LSF/MM/BPF TOPIC] eBFP for block devices
Date: Mon, 02 May 2022 13:45:55 -0400 [thread overview]
Message-ID: <87y1zjq14c.fsf@collabora.com> (raw)
In-Reply-To: <5276e9fa-a253-6195-e697-60b4ff6e9bc4@suse.de> (Hannes Reinecke's message of "Mon, 2 May 2022 09:21:31 -0700")
Hannes Reinecke <hare@suse.de> writes:
> 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.
Cc'ing Khazhy since Google might have some applications for this to
filter IOs based on the blocks being accessed, in the context of
safeguarding specific regions from accidental overwrites / application
error.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2022-05-02 17:46 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 [this message]
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
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=87y1zjq14c.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=hare@suse.de \
--cc=khazhy@google.com \
--cc=linux-block@vger.kernel.org \
--cc=osandov@fb.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