From: "Michael S. Tsirkin" <mst@redhat.com>
To: Angus Chen <angus.chen@jaguarmicro.com>
Cc: lingshan.zhu@intel.com, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] vDPA/ifcvf: fix the Calculation of queuepair
Date: Thu, 22 Sep 2022 07:43:38 -0400 [thread overview]
Message-ID: <20220922073959-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220922110017.2054-1-angus.chen@jaguarmicro.com>
Thanks! Let's see if we get an ack.
Minor things for the future (in case a new version will be needed):
Subject should include the patch version. Also pls avoid
capital letters in the middle of the sentence. E.g.
[PATCH v3] vDPA/ifcvf: fix the calculation of queuepair
On Thu, Sep 22, 2022 at 07:00:17PM +0800, Angus Chen wrote:
> The queuepair should be divided by 2
> It should not be hw->nr_vring when multi-queue feature was enabled
> fix commit 2ddae773c93b ("detect and use the onboard number ")
An extra " " here at the end.
It's also a good idea to add:
Fixes: 2ddae773c93b ("detect and use the onboard number")
>
> Signed-off-by: Angus Chen <angus.chen@jaguarmicro.com>
> ---
A good thing to add here is a changelog.
In this case the patch is unchanged, so you would write:
changes in v2:
- updated commit log with more info, addressing comments by MST
- no code changes
add more versions to this as you are revising the patch.
> drivers/vdpa/ifcvf/ifcvf_base.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/vdpa/ifcvf/ifcvf_base.c b/drivers/vdpa/ifcvf/ifcvf_base.c
> index 75a703b803a2..3e4486bfa0b7 100644
> --- a/drivers/vdpa/ifcvf/ifcvf_base.c
> +++ b/drivers/vdpa/ifcvf/ifcvf_base.c
> @@ -323,7 +323,7 @@ u16 ifcvf_get_vq_state(struct ifcvf_hw *hw, u16 qid)
> u32 q_pair_id;
>
> ifcvf_lm = (struct ifcvf_lm_cfg __iomem *)hw->lm_cfg;
> - q_pair_id = qid / hw->nr_vring;
> + q_pair_id = qid / 2;
> avail_idx_addr = &ifcvf_lm->vring_lm_cfg[q_pair_id].idx_addr[qid % 2];
> last_avail_idx = vp_ioread16(avail_idx_addr);
>
> @@ -337,7 +337,7 @@ int ifcvf_set_vq_state(struct ifcvf_hw *hw, u16 qid, u16 num)
> u32 q_pair_id;
>
> ifcvf_lm = (struct ifcvf_lm_cfg __iomem *)hw->lm_cfg;
> - q_pair_id = qid / hw->nr_vring;
> + q_pair_id = qid / 2;
> avail_idx_addr = &ifcvf_lm->vring_lm_cfg[q_pair_id].idx_addr[qid % 2];
> hw->vring[qid].last_avail_idx = num;
> vp_iowrite16(num, avail_idx_addr);
> --
> 2.17.1
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next parent reply other threads:[~2022-09-22 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220922110017.2054-1-angus.chen@jaguarmicro.com>
2022-09-22 11:43 ` Michael S. Tsirkin [this message]
2022-09-23 4:12 ` [PATCH] vDPA/ifcvf: fix the Calculation of queuepair Jason Wang
[not found] <TY2PR06MB34246957523C124C501790CD854E9@TY2PR06MB3424.apcprd06.prod.outlook.com>
2022-09-22 9:06 ` Michael S. Tsirkin
[not found] ` <33788b06-6c12-a9e3-4ae3-c817c0842bd3@intel.com>
2022-09-22 10:17 ` Michael S. Tsirkin
[not found] ` <b85f98df-62a5-7312-fcdb-12a6f1c61ae4@intel.com>
2022-09-23 5:27 ` Michael S. Tsirkin
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=20220922073959-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=angus.chen@jaguarmicro.com \
--cc=lingshan.zhu@intel.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 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.