DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "yuanzhiyuan0928@outlook.com" <yuanzhiyuan0928@outlook.com>,
	dev <dev@dpdk.org>, chenbox <chenbox@nvidia.com>
Subject: Re: 0001-vhost-optimize-vhost-user-get-protocol-features
Date: Mon, 10 Jun 2024 06:26:10 +0200	[thread overview]
Message-ID: <d590d54d-3990-4180-84e6-32da2f7eabc4@redhat.com> (raw)
In-Reply-To: <PH7PR03MB7047CABF56B5432EC62BD935A485A@PH7PR03MB7047.namprd03.prod.outlook.com>

Hello Yuan,

On 12/5/23 12:01, yuanzhiyuan0928@outlook.com wrote:
> From 4cf72842a07b2270876939fd2bb2367efaad95f4 Mon Sep 17 00:00:00 2001
> From: Yuan Zhiyuan <yuanzhiyuan0928@outlook.com>
> Date: Fri, 1 Dec 2023 11:27:51 +0000
> Subject: [PATCH] vhost: optimize vhost user get protocol features

Thanks for your contribution.

For the next time, I suggest you follow the contributions guidelines in
the documentation. This patch is not properly formatted.

For this time, I will reword the subject and commit message as follow:

vhost: remove unnecessary features fetch

vhost_user_get_protocol_features() does not need to know about Virtio 
features, but only about Vhost-user protocol features.

With this change:

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

Thanks,
Maxime

> variable features is unused in vhost_user_get_protocol_features.
> 
> Signed-off-by: Yuan Zhiyuan <yuanzhiyuan0928@outlook.com>
> ---
>   lib/vhost/vhost_user.c | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/lib/vhost/vhost_user.c b/lib/vhost/vhost_user.c
> index e36312181a..3e737eaf12 100644
> --- a/lib/vhost/vhost_user.c
> +++ b/lib/vhost/vhost_user.c
> @@ -2243,9 +2243,8 @@ vhost_user_get_protocol_features(struct virtio_net **pdev,
> int main_fd __rte_unused)
>   {
> struct virtio_net *dev = *pdev;
> -uint64_t features, protocol_features;
> +uint64_t protocol_features;
> 
> -rte_vhost_driver_get_features(dev->ifname, &features);
> rte_vhost_driver_get_protocol_features(dev->ifname, &protocol_features);
> 
> ctx->msg.payload.u64 = protocol_features;
> -- 
> 2.34.1
> 


  reply	other threads:[~2024-06-10  4:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <202312011945259414218@outlook.com>
2023-12-05 11:01 ` 0001-vhost-optimize-vhost-user-get-protocol-features yuanzhiyuan0928
2024-06-10  4:26   ` Maxime Coquelin [this message]
2024-06-12  8:28   ` 0001-vhost-optimize-vhost-user-get-protocol-features Maxime Coquelin
2023-12-01 11:45 0001-vhost-optimize-vhost-user-get-protocol-features yuanzhiyuan0928

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=d590d54d-3990-4180-84e6-32da2f7eabc4@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=yuanzhiyuan0928@outlook.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;
as well as URLs for NNTP newsgroup(s).