patches for DPDK stable branches
 help / color / mirror / Atom feed
From: <lironh@marvell.com>
To: <mattias.ronnblom@ericsson.com>, <jerinj@marvell.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>,
	Yuri Chipchev <yuric@marvell.com>,
	Liron Himi <lironh@marvell.com>
Subject: [dpdk-stable] [PATCH v2] event/dsw: fix enqueue burst return value
Date: Wed, 6 May 2020 23:18:37 +0300	[thread overview]
Message-ID: <20200506201837.24803-1-lironh@marvell.com> (raw)
In-Reply-To: <20200506110959.23049-1-lironh@marvell.com>

From: Yuri Chipchev <yuric@marvell.com>

The returned number from rte_event_enqueue_*()
wouldn't include events marked with RTE_EVENT_OP_RELEASE.

Fixes: 1c8e3caa3 ("event/dsw: add event scheduling and device start/stop")
Cc: stable@dpdk.org

Signed-off-by: Yuri Chipchev <yuric@marvell.com>
Reviewed-by: Liron Himi <lironh@marvell.com>
---
v2:
- update commit description

 drivers/event/dsw/dsw_event.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/event/dsw/dsw_event.c b/drivers/event/dsw/dsw_event.c
index e5e3597aa..611b36781 100644
--- a/drivers/event/dsw/dsw_event.c
+++ b/drivers/event/dsw/dsw_event.c
@@ -1231,7 +1231,7 @@ dsw_event_enqueue_burst_generic(struct dsw_port *source_port,
 	DSW_LOG_DP_PORT(DEBUG, source_port->id, "%d non-release events "
 			"accepted.\n", num_non_release);
 
-	return num_non_release;
+	return (num_non_release + num_release);
 }
 
 uint16_t
-- 
2.23.0


  parent reply	other threads:[~2020-05-06 18:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 11:09 [dpdk-stable] [PATCH] " lironh
2020-05-06 11:19 ` Mattias Rönnblom
2020-05-06 20:18 ` lironh [this message]
2020-05-07  6:09   ` [dpdk-stable] [PATCH v2] " Mattias Rönnblom
2020-05-14  7:15     ` [dpdk-stable] [dpdk-dev] " Jerin Jacob

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=20200506201837.24803-1-lironh@marvell.com \
    --to=lironh@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=stable@dpdk.org \
    --cc=yuric@marvell.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).