DPDK patches and discussions
 help / color / mirror / Atom feed
From: Yuan Wang <yuanx.wang@intel.com>
To: maxime.coquelin@redhat.com, chenbo.xia@intel.com
Cc: dev@dpdk.org, jiayu.hu@intel.com, xuan.ding@intel.com,
	yvonnex.yang@intel.com, sunil.pai.g@intel.com,
	yuanx.wang@intel.com
Subject: [RFC v2 2/2] example/vhost: support to clear in-flight packets for async dequeue
Date: Sat, 12 Mar 2022 01:34:14 +0800	[thread overview]
Message-ID: <20220311173414.93216-3-yuanx.wang@intel.com> (raw)
In-Reply-To: <20220311173414.93216-1-yuanx.wang@intel.com>

This patch allows vring_state_changed() to clear
in-flight dequeue packets.

Signed-off-by: Yuan Wang <yuanx.wang@intel.com>
---
 examples/vhost/main.c | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/examples/vhost/main.c b/examples/vhost/main.c
index d26e40ab73..04e7821322 100644
--- a/examples/vhost/main.c
+++ b/examples/vhost/main.c
@@ -1767,9 +1767,6 @@ vring_state_changed(int vid, uint16_t queue_id, int enable)
 	if (!vdev)
 		return -1;
 
-	if (queue_id != VIRTIO_RXQ)
-		return 0;
-
 	if (dma_bind[vid2socketid[vid]].dmas[queue_id].async_enabled) {
 		if (!enable)
 			vhost_clear_queue_thread_unsafe(vdev, queue_id);
-- 
2.25.1


      parent reply	other threads:[~2022-03-11  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 13:28 [RFC 0/2] support to clear in-flight packets for async Yuan Wang
2022-01-17 13:28 ` [RFC 1/2] vhost: support clear in-flight packets for async dequeue Yuan Wang
2022-01-17 13:28 ` [RFC 2/2] example/vhost: support to " Yuan Wang
2022-03-11 17:34 ` [RFC v2 0/2] support to clear in-flight packets for async Yuan Wang
2022-03-11 17:34   ` [RFC v2 1/2] vhost: support clear in-flight packets for async dequeue Yuan Wang
2022-03-28  6:08     ` Pai G, Sunil
2022-03-29  9:51       ` Wang, YuanX
2022-03-11 17:34   ` Yuan Wang [this message]

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=20220311173414.93216-3-yuanx.wang@intel.com \
    --to=yuanx.wang@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=jiayu.hu@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=sunil.pai.g@intel.com \
    --cc=xuan.ding@intel.com \
    --cc=yvonnex.yang@intel.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).