DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rahul Bhansali <rbhansali@marvell.com>
Cc: dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
	 Kiran Kumar K <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	 Satha Rao <skoteshwar@marvell.com>,
	jerinj@marvell.com
Subject: Re: [PATCH 2/2] net/cnxk: separate callback for Rx flush on CN10k
Date: Thu, 21 Sep 2023 08:14:22 +0530	[thread overview]
Message-ID: <CALBAE1MQcssDEYi5xijTwLP3pYUGyPf+VOxB0PNAJC5zciLM8A@mail.gmail.com> (raw)
In-Reply-To: <20230920101222.767408-2-rbhansali@marvell.com>

On Wed, Sep 20, 2023 at 5:01 PM Rahul Bhansali <rbhansali@marvell.com> wrote:
>
> In dev stop case, Rx packet flush callback uses LMT lines to bulk free
> of the meta buffers. If dev stop is called from non EAL core then LMT
> address will not be valid.
> To avoid this, A separate callback for Rx packets flush is added,
> which will use NPA aura free API on individual meta packets.
>
> Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>


Fix CI issues at
https://patchwork.dpdk.org/project/dpdk/patch/20230920101222.767408-2-rbhansali@marvell.com/

  reply	other threads:[~2023-09-21  2:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-20 10:12 [PATCH 1/2] common/cnxk: reserve last LMT line for control ops Rahul Bhansali
2023-09-20 10:12 ` [PATCH 2/2] net/cnxk: separate callback for Rx flush on CN10k Rahul Bhansali
2023-09-21  2:44   ` Jerin Jacob [this message]
2023-09-21 13:19 ` [PATCH v2] common/cnxk: reserve last LMT line for control ops Rahul Bhansali
2023-09-28  6:51   ` 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=CALBAE1MQcssDEYi5xijTwLP3pYUGyPf+VOxB0PNAJC5zciLM8A@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@marvell.com \
    --cc=rbhansali@marvell.com \
    --cc=skori@marvell.com \
    --cc=skoteshwar@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).