DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gagandeep Singh <g.singh@nxp.com>
To: dev@dpdk.org
Cc: Gagandeep Singh <g.singh@nxp.com>
Subject: [PATCH] kni: update kernel API to receive packets
Date: Thu, 14 Apr 2022 17:53:19 +0530	[thread overview]
Message-ID: <20220414122319.3519271-1-g.singh@nxp.com> (raw)

API 'netif_rx_ni()' has been removed in kernel with commit:
baebdf48c3600 ("net: dev: Makes sure netif_rx() can be invoked in any context.")

The API netif_rx() can be used for any context to receive packets
from device drivers.

This patch replaces the API netif_rx_ni() with netif_rx().

Signed-off-by: Gagandeep Singh <g.singh@nxp.com>
---
 kernel/linux/kni/kni_net.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kernel/linux/kni/kni_net.c b/kernel/linux/kni/kni_net.c
index 29e5b9e21f..e66b35314a 100644
--- a/kernel/linux/kni/kni_net.c
+++ b/kernel/linux/kni/kni_net.c
@@ -441,7 +441,7 @@ kni_net_rx_normal(struct kni_dev *kni)
 		skb->ip_summed = CHECKSUM_UNNECESSARY;
 
 		/* Call netif interface */
-		netif_rx_ni(skb);
+		netif_rx(skb);
 
 		/* Update statistics */
 		dev->stats.rx_bytes += len;
-- 
2.25.1


             reply	other threads:[~2022-04-14 12:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-14 12:23 Gagandeep Singh [this message]
2022-04-15  3:24 ` Harold Huang
2022-04-15  4:07   ` Gagandeep Singh
2022-04-15 12:30     ` Ferruh Yigit
2022-04-15 14:59       ` Stephen Hemminger
2022-04-18 11:33         ` Gagandeep Singh
2022-04-20  5:03 ` Gagandeep Singh
2022-04-20  7:45   ` Wang, Haiyue
2022-04-20 10:39     ` Gagandeep Singh
2022-04-21  3:45   ` [PATCH v2] " Gagandeep Singh
2022-04-21  8:29     ` Ferruh Yigit
2022-04-21  8:59     ` [PATCH v3] " Gagandeep Singh
2022-05-23  9:15       ` Min Hu (Connor)
2022-06-26 13:25       ` Thomas Monjalon

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=20220414122319.3519271-1-g.singh@nxp.com \
    --to=g.singh@nxp.com \
    --cc=dev@dpdk.org \
    /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).