[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8cf1aef0-ea5b-a3df-266d-ae67674c96ae@grimberg.me>
Date: Mon, 4 Jul 2022 17:00:10 +0300
From: Sagi Grimberg <sagi@...mberg.me>
To: Ming Lei <ming.lei@...hat.com>
Cc: Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org,
Harris James R <james.r.harris@...el.com>,
linux-kernel@...r.kernel.org, io-uring@...r.kernel.org,
Gabriel Krisman Bertazi <krisman@...labora.com>,
ZiyangZhang <ZiyangZhang@...ux.alibaba.com>,
Xiaoguang Wang <xiaoguang.wang@...ux.alibaba.com>,
Stefan Hajnoczi <stefanha@...hat.com>
Subject: Re: [PATCH V3 1/1] ublk: add io_uring based userspace block driver
>>> diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
>>> index fdb81f2794cd..d218089cdbec 100644
>>> --- a/drivers/block/Kconfig
>>> +++ b/drivers/block/Kconfig
>>> @@ -408,6 +408,12 @@ config BLK_DEV_RBD
>>> If unsure, say N.
>>> +config BLK_DEV_UBLK
>>> + bool "Userspace block driver"
>>
>> Really? why compile this to the kernel and not tristate as loadable
>> module?
>
> So far, this is only one reason: task_work_add() is required, which
> isn't exported for modules.
So why not exporting it?
Doesn't seem like a good justification to build it into the kernel.
Powered by blists - more mailing lists