From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Dongli Zhang <dongli.zhang@oracle.com>,
"Ewan D . Milne" <emilne@redhat.com>
Subject: Re: [PATCH V2] blk-mq: insert passthrough request into hctx->dispatch directly
Date: Wed, 26 Feb 2020 05:22:48 +0800 [thread overview]
Message-ID: <20200225212248.GA18633@ming.t460p> (raw)
In-Reply-To: <20200225155102.GA18299@infradead.org>
Hi Christoph,
On Tue, Feb 25, 2020 at 07:51:02AM -0800, Christoph Hellwig wrote:
> It would be really helpful if the commit log contained the explanation
> from your reply on the previous submission..
IMO, the issue isn't only on SCSI with ALUA which is just one example,
and it should happen on any situation in which FS request depends on
passthrough request. From this viewpoint, the commit log is enough,
and ALUA story may not be needed.
Thanks,
Ming
prev parent reply other threads:[~2020-02-25 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-25 1:04 [PATCH V2] blk-mq: insert passthrough request into hctx->dispatch directly Ming Lei
2020-02-25 1:51 ` Jens Axboe
2020-02-25 15:51 ` Christoph Hellwig
2020-02-25 21:22 ` Ming Lei [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=20200225212248.GA18633@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=dongli.zhang@oracle.com \
--cc=emilne@redhat.com \
--cc=hch@infradead.org \
--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