DPDK patches and discussions
 help / color / mirror / Atom feed
From: Syed Intekhab Anjum <syed.intekhab.anjum@gmail.com>
To: dev@dpdk.org
Subject: Can rte_eth_tx_burst frees buffer to external cache which could be configured during rte_eth_tx_queue_setup
Date: Thu, 6 Jun 2024 20:07:14 +0530	[thread overview]
Message-ID: <CAGYJO=MJZYtRD+OcDwjJ13dOcVvatWY2B6qogi835=5QnwyHjQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Hi,

Does DPDK support to free the transmitted buffers to external cache which
is provided during tx queue configurations (rte_eth_tx_queue_setup).

This is needed to extract better performance when multiple tx queues are
being worked on by unregistered non-eal pthreads which sends the packets
(mbuf from common rte_mempool) to the queue parallelly using
rte_eth_tx_burst.

Otherwise, they are bypassed frim local cache and go to the path of CAS
operation on the common pool for free operation.

Or is there any other way to achieve this?


Thanks

Syed

[-- Attachment #2: Type: text/html, Size: 2803 bytes --]

                 reply	other threads:[~2024-06-10 15:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAGYJO=MJZYtRD+OcDwjJ13dOcVvatWY2B6qogi835=5QnwyHjQ@mail.gmail.com' \
    --to=syed.intekhab.anjum@gmail.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).