From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <tom.leiming@gmail.com>
Cc: "jianchao.wang" <jianchao.w.wang@oracle.com>,
Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
James Bottomley <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-block <linux-block@vger.kernel.org>,
Linux SCSI List <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] block: export __blk_complete_request
Date: Fri, 15 Jun 2018 13:58:19 +0200 [thread overview]
Message-ID: <20180615115819.GA25694@lst.de> (raw)
In-Reply-To: <CACVXFVMPAdFbX3x-KUjHCQhb_rT6p9ROYHg63aUtEqdbitEaKQ@mail.gmail.com>
On Fri, Jun 15, 2018 at 11:20:40AM +0800, Ming Lei wrote:
> > but blk_mq_check_expired doesn't do that.
> > do I miss anything ?
>
> Right, that is the difference between blk-mq and legacy now, then if scsi-mq
> drivers can work well, they should work well with the following change in the
> non-mq mode:
We'll still need referene counting against reuse and/or premature
freeing of requests.
next prev parent reply other threads:[~2018-06-15 11:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 1:57 [PATCH 1/2] block: export __blk_complete_request Jianchao Wang
2018-06-15 1:57 ` [PATCH 2/2] scsi_transport_fc: use __blk_complete_request in fc_bsg_job_timeout Jianchao Wang
2018-06-15 2:17 ` [PATCH 1/2] block: export __blk_complete_request Ming Lei
2018-06-15 2:22 ` jianchao.wang
2018-06-15 2:44 ` jianchao.wang
2018-06-15 2:56 ` Ming Lei
2018-06-15 3:04 ` jianchao.wang
2018-06-15 3:20 ` Ming Lei
2018-06-15 3:26 ` jianchao.wang
2018-06-15 4:03 ` Ming Lei
2018-06-15 5:10 ` jianchao.wang
2018-06-15 11:58 ` Christoph Hellwig [this message]
2018-06-15 2:49 ` Ming Lei
2018-06-19 14:09 ` Christoph Hellwig
2018-06-19 14:09 ` Christoph Hellwig
2018-06-19 14:52 ` jianchao.wang
2018-06-19 14:52 ` jianchao.wang
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=20180615115819.GA25694@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=jejb@linux.vnet.ibm.com \
--cc=jianchao.w.wang@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tom.leiming@gmail.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.