From: Pavel Machek <pavel@ucw.cz>
To: Ming Lei <ming.lei@redhat.com>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Gabriel Krisman Bertazi <krisman@collabora.com>,
lsf-pc@lists.linux-foundation.org, linux-block@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] block drivers in user space
Date: Thu, 28 Jul 2022 10:23:07 +0200 [thread overview]
Message-ID: <20220728082307.GA15112@duo.ucw.cz> (raw)
In-Reply-To: <YqFx2GGACopPmLaM@T590>
[-- Attachment #1: Type: text/plain, Size: 779 bytes --]
Hi!
> > > If you have actual report, I am happy to take account into it, otherwise not
> > > sure if it is worth of time/effort in thinking/addressing one pure theoretical
> > > concern.
> >
> > Hi Ming,
> >
> > Thanks for your look & reply.
> >
> > That is not a wild guess. That is a basic difference between
> > in-kernel native block-based drivers and user-space block drivers.
>
> Please look at my comment, wrt. your pure theoretical concern, userspace
> block driver is same with kernel loop/nbd.
>
> Did you see such report on loop & nbd? Can you answer my questions wrt.
> kernel thread B?
Yes, nbd is known to deadlock under high loads. Don't do that.
Pavel
--
People of Russia, stop Putin before his war on Ukraine escalates.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-07-28 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YhXMu/GcceyDx637@B-P7TQMD6M-0146.local>
[not found] ` <a55211a1-a610-3d86-e21a-98751f20f21e@opensource.wdc.com>
[not found] ` <YhXsQdkOpBY2nmFG@B-P7TQMD6M-0146.local>
[not found] ` <3702afe7-2918-42e7-110b-efa75c0b58e8@opensource.wdc.com>
[not found] ` <YhbYOeMUv5+U1XdQ@B-P7TQMD6M-0146.local>
2022-06-09 2:01 ` [LSF/MM/BPF TOPIC] block drivers in user space Ming Lei
2022-06-09 2:28 ` Gao Xiang
2022-06-09 4:06 ` Ming Lei
2022-06-09 4:55 ` Gao Xiang
2022-06-10 1:52 ` Ming Lei
2022-07-28 8:23 ` Pavel Machek [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=20220728082307.GA15112@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=damien.lemoal@opensource.wdc.com \
--cc=krisman@collabora.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=ming.lei@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).