Hi Christoph,
I love your patch! Yet something to improve:
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.19-rc7]
[cannot apply to next-20181010]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.co
On Wed, Oct 10 2018 at 10:15am -0400,
Mike Snitzer wrote:
> On Tue, Oct 09 2018 at 9:52pm -0400,
> Damien Le Moal wrote:
>
> > From: Christoph Hellwig
> >
> > Dispatching a report zones command through the request queue is a major
> > pain due to the command reply payload rewriting necessary
On Tue, Oct 09 2018 at 9:52pm -0400,
Damien Le Moal wrote:
> From: Christoph Hellwig
>
> Dispatching a report zones command through the request queue is a major
> pain due to the command reply payload rewriting necessary. Given that
> blkdev_report_zones() is executing everything synchronously
Hi Christoph,
I love your patch! Yet something to improve:
[auto build test ERROR on block/for-next]
[also build test ERROR on v4.19-rc7]
[cannot apply to next-20181010]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.co
On Tue, Oct 09 2018 at 9:52pm -0400,
Damien Le Moal wrote:
> From: Christoph Hellwig
>
> Dispatching a report zones command through the request queue is a major
> pain due to the command reply payload rewriting necessary. Given that
> blkdev_report_zones() is executing everything synchronously
From: Christoph Hellwig
Dispatching a report zones command through the request queue is a major
pain due to the command reply payload rewriting necessary. Given that
blkdev_report_zones() is executing everything synchronously, implement
report zones as a block device file operation instead, allow
6 matches
Mail list logo
