From: Ming Lei <ming.lei@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
Mike Christie <michael.christie@oracle.com>
Cc: bvanassche@acm.org, lduncan@suse.com, cleech@redhat.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
james.bottomley@hansenpartnership.com
Subject: Re: [RFC PATCH 0/4] scsi/iscsi: Send iscsi data from kblockd
Date: Wed, 16 Mar 2022 09:08:55 +0800 [thread overview]
Message-ID: <YjE4p4qlNgd0TyVM@T590> (raw)
In-Reply-To: <YjBNwMp3WlkjFd0g@infradead.org>
On Tue, Mar 15, 2022 at 01:26:40AM -0700, Christoph Hellwig wrote:
> The subject seems a bit misleading, I'd expect to see
> BLK_MQ_F_BLOCKING in the subject.
>
> Note that you'll also need the series from Ming to support dm-multipath
> on top devices that set BLK_MQ_F_BLOCKING.
Indeed.
Mike, please feel free to fold the following patches into your next
post:
https://lore.kernel.org/linux-block/YcP4FMG9an5ReIiV@T590/#r
Thanks,
Ming
prev parent reply other threads:[~2022-03-16 1:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 0:39 [RFC PATCH 0/4] scsi/iscsi: Send iscsi data from kblockd Mike Christie
2022-03-08 0:39 ` [RFC PATCH 1/4] scsi: Allow drivers to set BLK_MQ_F_BLOCKING Mike Christie
2022-03-08 4:57 ` Bart Van Assche
2022-03-08 7:00 ` Daejun Park
2022-03-08 16:14 ` Mike Christie
2022-03-09 0:53 ` Ming Lei
2022-03-09 1:17 ` Mike Christie
2022-03-09 1:43 ` Ming Lei
2022-03-09 19:38 ` Mike Christie
2022-03-08 0:39 ` [RFC PATCH 2/4] scsi: iscsi: Tell drivers when we must not block Mike Christie
2022-03-08 4:59 ` Bart Van Assche
2022-03-08 15:58 ` Mike Christie
2022-03-08 0:39 ` [RFC PATCH 3/4] scsi: iscsi: Support transmit from queuecommand Mike Christie
2022-03-08 0:39 ` [RFC PATCH 4/4] scsi: iscsi_tcp: Allow user to control if " Mike Christie
2022-03-08 5:10 ` Bart Van Assche
2022-03-08 16:51 ` Mike Christie
2022-03-15 8:26 ` [RFC PATCH 0/4] scsi/iscsi: Send iscsi data from kblockd Christoph Hellwig
2022-03-16 1:08 ` 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=YjE4p4qlNgd0TyVM@T590 \
--to=ming.lei@redhat.com \
--cc=bvanassche@acm.org \
--cc=cleech@redhat.com \
--cc=hch@infradead.org \
--cc=james.bottomley@hansenpartnership.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox