DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, <dev@dpdk.org>
Cc: <stable@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>,
	Helin Zhang <helin.zhang@intel.com>,
	Gagandeep Singh <g.singh@nxp.com>,
	Mingli Yu <mingli.yu@windriver.com>
Subject: Re: [PATCH] kni: fix compile error
Date: Mon, 23 May 2022 09:43:20 +0100	[thread overview]
Message-ID: <2e53a12c-dda4-bce8-3b6f-60c2c00f5056@amd.com> (raw)
In-Reply-To: <20220521070642.35413-1-humin29@huawei.com>

On 5/21/2022 8:06 AM, Min Hu (Connor) wrote:
> [CAUTION: External Email]
> 
> When kernel version change into 5.18 from 5.17, 'netif_rx_ni' is discard.
> It is replaced by 'netif_rx' and this API is also supported in the
> version below 5.18.
> 
> This patch fixed it.
> 
> Fixes: d89a58dfe90b ("kni: support chained mbufs")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> ---
>   kernel/linux/kni/kni_net.c | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/linux/kni/kni_net.c b/kernel/linux/kni/kni_net.c
> index 29e5b9e21f..e19f03285e 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);
> 

Hi Connor,

There is already a patch for this [1], can you test & ack that instead 
please?

Same for Mingli's patch [2], @Mingli, can you please test and ack the 
[1] instead?

[1] kni: update kernel API to receive packets
https://patches.dpdk.org/project/dpdk/patch/20220421085931.2429443-1-g.singh@nxp.com/
http://inbox.dpdk.org/dev/20220421085931.2429443-1-g.singh@nxp.com/


[2]
https://patches.dpdk.org/project/dpdk/patch/20220511112334.3233433-1-mingli.yu@windriver.com/

>                  /* Update statistics */
>                  dev->stats.rx_bytes += len;
> @@ -779,7 +779,7 @@ kni_net_set_mac(struct net_device *netdev, void *p)
>                  return -EADDRNOTAVAIL;
> 
>          memcpy(req.mac_addr, addr->sa_data, netdev->addr_len);
> -       memcpy(netdev->dev_addr, addr->sa_data, netdev->addr_len);
> +       memcpy((void *)(netdev->dev_addr), addr->sa_data, netdev->addr_len);

Why don't you use new helper functions instead? I can see not using 
helper function is causing other problem as well [3].

[3]
https://patches.dpdk.org/project/dpdk/patch/20220407082544.21282-1-humin29@huawei.com/

> 
>          ret = kni_net_process_request(netdev, &req);
> 
> --
> 2.33.0
> 


  reply	other threads:[~2022-05-23  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21  7:06 Min Hu (Connor)
2022-05-23  8:43 ` Ferruh Yigit [this message]
2022-05-31 16:42 ` Andrew Rybchenko
2022-06-01  1:52   ` Min Hu (Connor)
2022-06-01  8:47     ` Andrew Rybchenko
2022-06-01 15:49       ` 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=2e53a12c-dda4-bce8-3b6f-60c2c00f5056@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=g.singh@nxp.com \
    --cc=helin.zhang@intel.com \
    --cc=humin29@huawei.com \
    --cc=mingli.yu@windriver.com \
    --cc=stable@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).