From: ming.lei@redhat.com (Ming Lei)
Subject: [PATCH] nvme-pci: fix single segment detection
Date: Thu, 9 May 2019 19:24:12 +0800 [thread overview]
Message-ID: <20190509112410.GA20711@ming.t460p> (raw)
In-Reply-To: <20190509110409.19647-1-hch@lst.de>
On Thu, May 09, 2019@01:04:09PM +0200, Christoph Hellwig wrote:
> blk_rq_nr_phys_segments isn't exactly accurate at the request/bio
> level, so work around that fact with a few crude sanity checks. To
> be fixed for real in the block layer soon.
>
> Fixes: 297910571f08 ("nvme-pci: optimize mapping single segment requests using SGLs")
> Signed-off-by: Christoph Hellwig <hch at lst.de>
> ---
> drivers/nvme/host/pci.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c
> index 2a8708c9ac18..9a4253be2723 100644
> --- a/drivers/nvme/host/pci.c
> +++ b/drivers/nvme/host/pci.c
> @@ -824,7 +824,15 @@ static blk_status_t nvme_map_data(struct nvme_dev *dev, struct request *req,
> blk_status_t ret = BLK_STS_RESOURCE;
> int nr_mapped;
>
> - if (blk_rq_nr_phys_segments(req) == 1) {
> + /*
> + * Crude hack to work around the block layer accounting for the fact
> + * that the SG mapping can merge multiple physically contigous segments
> + * in blk_rq_nr_phys_segments() despite the fact that not everyone is
> + * mapping the request to a scatterlist. To be fixed for real in the
> + * block layer eventually..
> + */
> + if (blk_rq_nr_phys_segments(req) == 1 &&
> + !req->bio->bi_next && req->bio->bi_vcnt == 1) {
> struct bio_vec bv = req_bvec(req);
I'd suggest to fix block layer instead of working around the issue here,
then any driver may benefit from the fix.
Especially checking bio->bi_vcnt is just a hack, and drivers should
never use .bi_vcnt.
Thanks,
Ming
next prev parent reply other threads:[~2019-05-09 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 11:04 [PATCH] nvme-pci: fix single segment detection Christoph Hellwig
2019-05-09 11:24 ` Ming Lei [this message]
2019-05-09 12:34 ` Christoph Hellwig
2019-05-09 13:31 ` Ming Lei
2019-05-13 6:26 ` Christoph Hellwig
2019-05-12 15:20 ` Sagi Grimberg
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=20190509112410.GA20711@ming.t460p \
--to=ming.lei@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox