From: Michal Krawczyk <mk@semihalf.com>
To: mk@semihalf.com, mw@semihalf.com, gtzalik@amazon.com,
zorik@amazon.com, matua@amazon.com
Cc: dev@dpdk.org, stable@dpdk.org, Stewart Allen <allenste@amazon.com>
Subject: [dpdk-dev] [PATCH 2/3] net/ena: fix passing RSS hash to mbuf
Date: Thu, 25 Oct 2018 19:59:22 +0200 [thread overview]
Message-ID: <20181025175923.10858-3-mk@semihalf.com> (raw)
In-Reply-To: <20181025175923.10858-1-mk@semihalf.com>
The driver was passing to the mbuf Rx queue ID instead of hash received
from the device. Now, the RSS hash from the Rx descriptor is being set.
Fixes: 1173fca25af9 ("ena: add polling-mode driver")
Cc: stable@dpdk.org
Signed-off-by: Stewart Allen <allenste@amazon.com>
Acked-by: Michal Krawczyk <mk@semihalf.com>
---
drivers/net/ena/ena_ethdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ena/ena_ethdev.c b/drivers/net/ena/ena_ethdev.c
index 186ab0e6b..191153a8f 100644
--- a/drivers/net/ena/ena_ethdev.c
+++ b/drivers/net/ena/ena_ethdev.c
@@ -1910,7 +1910,7 @@ static uint16_t eth_ena_recv_pkts(void *rx_queue, struct rte_mbuf **rx_pkts,
/* fill mbuf attributes if any */
ena_rx_mbuf_prepare(mbuf_head, &ena_rx_ctx);
- mbuf_head->hash.rss = (uint32_t)rx_ring->id;
+ mbuf_head->hash.rss = ena_rx_ctx.hash;
/* pass to DPDK application head mbuf */
rx_pkts[recv_idx] = mbuf_head;
--
2.14.1
next prev parent reply other threads:[~2018-10-25 17:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 17:59 [dpdk-dev] [PATCH 0/3] net/ena: upgrade to v1.1.1 Michal Krawczyk
2018-10-25 17:59 ` [dpdk-dev] [PATCH 1/3] net/ena: recreate HW IO rings on start and stop Michal Krawczyk
2018-10-25 17:59 ` Michal Krawczyk [this message]
2018-10-25 17:59 ` [dpdk-dev] [PATCH 3/3] net/ena: change version to v1.1.1 Michal Krawczyk
2018-10-26 14:36 ` [dpdk-dev] [PATCH 0/3] net/ena: upgrade " Ferruh Yigit
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=20181025175923.10858-3-mk@semihalf.com \
--to=mk@semihalf.com \
--cc=allenste@amazon.com \
--cc=dev@dpdk.org \
--cc=gtzalik@amazon.com \
--cc=matua@amazon.com \
--cc=mw@semihalf.com \
--cc=stable@dpdk.org \
--cc=zorik@amazon.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).