DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: John Alexander <John.Alexander@datapath.co.uk>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Transmit Completion
Date: Tue, 2 Mar 2021 07:53:10 -0800
Message-ID: <20210302075310.58c9da1c@hermes.local> (raw)
In-Reply-To: <AM9PR09MB4900085829B124A0AACE3C58B4999@AM9PR09MB4900.eurprd09.prod.outlook.com>

On Tue, 2 Mar 2021 10:26:24 +0000
John Alexander <John.Alexander@datapath.co.uk> wrote:

> Hi,
> 
> Once a packet has been transmitted using an API call such as rte_eth_tx_burst(), what is the preferred method of determining that the packet has been transmitted?  I need to provide a notification to an application so that it can re-use/re-claim some application resources that were associated with the mbuf in the mbuf custom private data; this is a lazy re-claim, we're not after immediate per-packets events just eventual reclaim.
> 
> I've been finding that rte_eth_tx_done_cleanup() isn't very widely supported by many PMDs and when used with the Intel i40e PMD, it doesn't flush out mbufs where the associated descriptor hasn't yet been updated due to the descriptor update granularity (setting that down to 1 seems to result in at least 1 mbuf still remaining stuck in the PMD).  The reclaim cycle works fine when I'm continually sending, when I pause or stop sending, I never get my mbufs back so I'm wondering what the preferred way of achieving this is?
> 
> Many Thanks,
> John A.
> 
> 

DPDK has no such mechanism built in.
You might be able to do something like this by creating a new memory pool
type and doing an action in the mempool enqueue operation.

Transmit done -> rte_pktmbuf_free -> rte_mempool_put
calls mempool_ops->enqueue


  reply	other threads:[~2021-03-02 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 10:26 John Alexander
2021-03-02 15:53 ` Stephen Hemminger [this message]
2021-03-02 16:22 ` Tom Barbette

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=20210302075310.58c9da1c@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=John.Alexander@datapath.co.uk \
    --cc=users@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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git