All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, dm-devel@redhat.com,
	Ming Lei <ming.lei@redhat.com>
Subject: Re: [dm-devel] [PATCH 0/3] blk-mq/dm-rq: support BLK_MQ_F_BLOCKING for dm-rq
Date: Mon, 17 Jan 2022 00:08:32 -0800	[thread overview]
Message-ID: <YeUkABLBcStfJxNp@infradead.org> (raw)
In-Reply-To: <Yd2tDWuP+aT3Hxbj@redhat.com>

On Tue, Jan 11, 2022 at 11:15:09AM -0500, Mike Snitzer wrote:
> Round and round we go.. Pretty tired of this.

Same here.

> You are perfectly fine with incrementally compromising request-based
> DM's ability to evolve as block core does.

I would not word it that way, but I think we mean the same thing.  Yes,
I do not want to add more hooks for a complete oddball that has no
actual use case.  dm-rq does a good enough job for SCSI and has all
the infrastucture for it.  We should not more cruft to exteded it to
use cases for which there is no consesus and which are much better
covered by alredy existing code in the kernel.

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jens Axboe <axboe@kernel.dk>,
	dm-devel@redhat.com, linux-block@vger.kernel.org,
	Ming Lei <ming.lei@redhat.com>
Subject: Re: [dm-devel] [PATCH 0/3] blk-mq/dm-rq: support BLK_MQ_F_BLOCKING for dm-rq
Date: Mon, 17 Jan 2022 00:08:32 -0800	[thread overview]
Message-ID: <YeUkABLBcStfJxNp@infradead.org> (raw)
In-Reply-To: <Yd2tDWuP+aT3Hxbj@redhat.com>

On Tue, Jan 11, 2022 at 11:15:09AM -0500, Mike Snitzer wrote:
> Round and round we go.. Pretty tired of this.

Same here.

> You are perfectly fine with incrementally compromising request-based
> DM's ability to evolve as block core does.

I would not word it that way, but I think we mean the same thing.  Yes,
I do not want to add more hooks for a complete oddball that has no
actual use case.  dm-rq does a good enough job for SCSI and has all
the infrastucture for it.  We should not more cruft to exteded it to
use cases for which there is no consesus and which are much better
covered by alredy existing code in the kernel.

--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel


  reply	other threads:[~2022-01-17  8:08 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-21 14:14 [PATCH 0/3] blk-mq/dm-rq: support BLK_MQ_F_BLOCKING for dm-rq Ming Lei
2021-12-21 14:14 ` [dm-devel] " Ming Lei
2021-12-21 14:14 ` [PATCH 1/3] block: split having srcu from queue blocking Ming Lei
2021-12-21 14:14   ` [dm-devel] " Ming Lei
2022-01-11 18:13   ` Jeff Moyer
2022-01-11 18:13     ` Jeff Moyer
2021-12-21 14:14 ` [PATCH 2/3] block: add blk_alloc_disk_srcu Ming Lei
2021-12-21 14:14   ` [dm-devel] " Ming Lei
2022-01-11 18:13   ` Jeff Moyer
2022-01-11 18:13     ` Jeff Moyer
2021-12-21 14:14 ` [PATCH 3/3] dm: mark dm queue as blocking if any underlying is blocking Ming Lei
2021-12-21 14:14   ` [dm-devel] " Ming Lei
2022-01-06 15:40   ` Mike Snitzer
2022-01-06 15:40     ` [dm-devel] " Mike Snitzer
2022-01-06 15:51     ` Ming Lei
2022-01-06 15:51       ` [dm-devel] " Ming Lei
2022-01-10 19:23       ` Mike Snitzer
2022-01-10 19:23         ` [dm-devel] " Mike Snitzer
2022-01-11 18:14   ` Jeff Moyer
2022-01-11 18:14     ` Jeff Moyer
2021-12-21 16:21 ` [PATCH 0/3] blk-mq/dm-rq: support BLK_MQ_F_BLOCKING for dm-rq Christoph Hellwig
2021-12-21 16:21   ` [dm-devel] " Christoph Hellwig
2021-12-23  4:16   ` Ming Lei
2021-12-23  4:16     ` [dm-devel] " Ming Lei
2021-12-28 21:30     ` Mike Snitzer
2021-12-28 21:30       ` [dm-devel] " Mike Snitzer
2022-01-10 19:26       ` Mike Snitzer
2022-01-10 19:26         ` [dm-devel] " Mike Snitzer
2022-01-11  8:34       ` Christoph Hellwig
2022-01-11  8:34         ` Christoph Hellwig
2022-01-11 16:15         ` Mike Snitzer
2022-01-11 16:15           ` [dm-devel] " Mike Snitzer
2022-01-17  8:08           ` Christoph Hellwig [this message]
2022-01-17  8:08             ` Christoph Hellwig
2022-01-11 18:23         ` Jeff Moyer
2022-01-11 18:23           ` Jeff Moyer
2022-01-17  8:10           ` Christoph Hellwig
2022-01-17  8:10             ` Christoph Hellwig
2022-01-19 21:03             ` Mike Snitzer
2022-01-19 21:03               ` [dm-devel] " Mike Snitzer

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=YeUkABLBcStfJxNp@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=snitzer@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 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.