DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: vanshika.shukla@nxp.com
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Jun Yang <jun.yang@nxp.com>
Subject: Re: [v2 10/10] bus/dpaa: optimize qman enqueue check
Date: Tue, 3 Jun 2025 19:51:38 -0700	[thread overview]
Message-ID: <20250603195138.310a98a5@hermes.local> (raw)
In-Reply-To: <20250602131526.3233959-11-vanshika.shukla@nxp.com>

On Mon,  2 Jun 2025 18:45:26 +0530
vanshika.shukla@nxp.com wrote:

> From: Hemant Agrawal <hemant.agrawal@nxp.com>
> 
> This patch improves data access during qman enequeue ring check.
> 
> Signed-off-by: Jun Yang <jun.yang@nxp.com>
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>

Still has compile failures, fix and resubmit

      reply	other threads:[~2025-06-04  2:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-28 10:39 [v1 00/10] DPAA specific fixes vanshika.shukla
2025-05-28 10:39 ` [v1 01/10] bus/dpaa: avoid using same structure and variable name vanshika.shukla
2025-05-28 10:39 ` [v1 02/10] bus/dpaa: add FMan node vanshika.shukla
2025-05-28 10:39 ` [v1 03/10] bus/dpaa: enhance DPAA SoC version vanshika.shukla
2025-05-28 14:28   ` Stephen Hemminger
2025-05-28 10:39 ` [v1 04/10] bus/dpaa: optimize bman acquire/release vanshika.shukla
2025-05-28 14:30   ` Stephen Hemminger
2025-05-28 14:50     ` [EXT] " Jun Yang
2025-05-28 10:39 ` [v1 05/10] mempool/dpaa: fast acquire and release vanshika.shukla
2025-05-28 10:39 ` [v1 06/10] mempool/dpaa: adjust pool element for LS1043A errata vanshika.shukla
2025-05-28 10:39 ` [v1 07/10] net/dpaa: add Tx rate limiting DPAA PMD API vanshika.shukla
2025-06-03  6:06   ` Varghese, Vipin
2025-05-28 10:39 ` [v1 08/10] net/dpaa: add devargs for enabling err packets on main queue vanshika.shukla
2025-05-28 10:39 ` [v1 09/10] bus/dpaa: improve DPAA cleanup vanshika.shukla
2025-05-28 10:39 ` [v1 10/10] bus/dpaa: optimize qman enqueue check vanshika.shukla
2025-06-02 13:15 ` [v2 00/10] DPAA specific fixes vanshika.shukla
2025-06-02 13:15   ` [v2 01/10] bus/dpaa: avoid using same structure and variable name vanshika.shukla
2025-06-02 13:15   ` [v2 02/10] bus/dpaa: add FMan node vanshika.shukla
2025-06-02 13:15   ` [v2 03/10] bus/dpaa: enhance DPAA SoC version vanshika.shukla
2025-06-02 13:15   ` [v2 04/10] bus/dpaa: optimize bman acquire/release vanshika.shukla
2025-06-02 13:15   ` [v2 05/10] mempool/dpaa: fast acquire and release vanshika.shukla
2025-06-02 13:15   ` [v2 06/10] mempool/dpaa: adjust pool element for LS1043A errata vanshika.shukla
2025-06-02 13:15   ` [v2 07/10] net/dpaa: add Tx rate limiting DPAA PMD API vanshika.shukla
2025-06-02 13:15   ` [v2 08/10] net/dpaa: add devargs for enabling err packets on main queue vanshika.shukla
2025-06-02 13:15   ` [v2 09/10] bus/dpaa: improve DPAA cleanup vanshika.shukla
2025-06-02 13:15   ` [v2 10/10] bus/dpaa: optimize qman enqueue check vanshika.shukla
2025-06-04  2:51     ` Stephen Hemminger [this message]

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=20250603195138.310a98a5@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jun.yang@nxp.com \
    --cc=sachin.saxena@nxp.com \
    --cc=vanshika.shukla@nxp.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).