DPDK patches and discussions
 help / color / mirror / Atom feed
From: "yuanzhiyuan0928@outlook.com" <yuanzhiyuan0928@outlook.com>
To: dev <dev@dpdk.org>, maxime.coquelin <maxime.coquelin@redhat.com>,
	 chenbox <chenbox@nvidia.com>
Subject: 0001-vhost-optimize-vhost-user-get-protocol-features
Date: Fri, 1 Dec 2023 19:45:30 +0800	[thread overview]
Message-ID: <PH7PR03MB70478C1ABD48CCBFBB51EA75A481A@PH7PR03MB7047.namprd03.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1061 bytes --]

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

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




yuanzhiyuan0928@outlook.com

[-- Attachment #1.2: Type: text/html, Size: 2511 bytes --]

[-- Attachment #2: 0001-vhost-optimize-vhost-user-get-protocol-features.patch --]
[-- Type: application/octet-stream, Size: 998 bytes --]

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

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:[~2023-12-01 11:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01 11:45 yuanzhiyuan0928 [this message]
     [not found] <202312011945259414218@outlook.com>
2023-12-05 11:01 ` 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=PH7PR03MB70478C1ABD48CCBFBB51EA75A481A@PH7PR03MB7047.namprd03.prod.outlook.com \
    --to=yuanzhiyuan0928@outlook.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@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;
as well as URLs for NNTP newsgroup(s).