linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "jianchao.wang" <jianchao.w.wang@oracle.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Bart Van Assche <bvanassche@acm.org>
Subject: Re: block: fix direct dispatch issue failure for clones
Date: Thu, 6 Dec 2018 21:10:53 -0500	[thread overview]
Message-ID: <20181207021053.GA17585@redhat.com> (raw)
In-Reply-To: <20181207015830.GC17427@redhat.com>

On Thu, Dec 06 2018 at  8:58pm -0500,
Mike Snitzer <snitzer@redhat.com> wrote:

> DM is forced to worry about all these details, as covered some in
> the header for commit 396eaf21ee17c476e8f66249fb1f4a39003d0ab4, it is
> trying to have its cake and eat it too.

Gah, obviously meant: DM is _NOT_ trying to have its cake and eat it too.

> It just wants IO scheduling to work for request-based DM devices.

  parent reply	other threads:[~2018-12-07  2:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-06 22:20 [PATCH] block: fix direct dispatch issue failure for clones Jens Axboe
2018-12-06 22:21 ` Jens Axboe
2018-12-06 22:46   ` Bart Van Assche
2018-12-06 22:28 ` Mike Snitzer
2018-12-06 22:32   ` Jens Axboe
2018-12-07  1:04 ` [PATCH] " jianchao.wang
2018-12-07  1:13   ` Jens Axboe
2018-12-07  1:22     ` jianchao.wang
2018-12-07  1:34       ` Jens Axboe
2018-12-07  1:58         ` Mike Snitzer
2018-12-07  2:06           ` Jens Axboe
2018-12-07  2:16             ` Jens Axboe
2018-12-07  2:28               ` Jens Axboe
2018-12-07  2:10           ` Mike Snitzer [this message]
2018-12-07  2:05         ` [PATCH] " jianchao.wang
2018-12-07  1:41     ` Mike Snitzer
2018-12-07  1:20   ` 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=20181207021053.GA17585@redhat.com \
    --to=snitzer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=jianchao.w.wang@oracle.com \
    --cc=linux-block@vger.kernel.org \
    /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).