From: Dongli Zhang <dongli.zhang@oracle.com>
To: virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: mst@redhat.com, jasowang@redhat.com, axboe@kernel.dk
Subject: Re: [PATCH 1/1] virtio_blk: replace 0 by HCTX_TYPE_DEFAULT to index blk_mq_tag_set->map
Date: Mon, 8 Apr 2019 22:00:45 +0800 [thread overview]
Message-ID: <630416d0-7eb0-656b-b780-74a84e2f7dc2@oracle.com> (raw)
In-Reply-To: <1552354316-20204-1-git-send-email-dongli.zhang@oracle.com>
ping?
The similar patchset has been queued by linux-scsi 5.2/scsi-queue.
virtio-blk is the last place where HCTX_TYPE_DEFAULT is hardcoded.
It would be more friendly to cscope if the hardcoding is avoided.
Thank you very much!
Dongli Zhang
On 03/12/2019 09:31 AM, Dongli Zhang wrote:
> Use HCTX_TYPE_DEFAULT instead of 0 to avoid hardcoding.
>
> Signed-off-by: Dongli Zhang <dongli.zhang@oracle.com>
> ---
> This is the only place to cleanup under drivers/block/*. Another patch set
> is sent to scsi and then all of below are cleaned up:
> - block/*
> - drivers/*
>
> drivers/block/virtio_blk.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c
> index 4bc083b..bed6035 100644
> --- a/drivers/block/virtio_blk.c
> +++ b/drivers/block/virtio_blk.c
> @@ -691,7 +691,8 @@ static int virtblk_map_queues(struct blk_mq_tag_set *set)
> {
> struct virtio_blk *vblk = set->driver_data;
>
> - return blk_mq_virtio_map_queues(&set->map[0], vblk->vdev, 0);
> + return blk_mq_virtio_map_queues(&set->map[HCTX_TYPE_DEFAULT],
> + vblk->vdev, 0);
> }
>
> #ifdef CONFIG_VIRTIO_BLK_SCSI
>
next prev parent reply other threads:[~2019-04-08 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 1:31 Dongli Zhang
2019-04-08 14:00 ` Dongli Zhang [this message]
2019-04-08 14:08 ` Jens Axboe
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=630416d0-7eb0-656b-b780-74a84e2f7dc2@oracle.com \
--to=dongli.zhang@oracle.com \
--cc=axboe@kernel.dk \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®