From: Tom Barbette <barbette@kth.se>
To: John Alexander <John.Alexander@datapath.co.uk>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Transmit Completion
Date: Tue, 2 Mar 2021 17:22:12 +0100 [thread overview]
Message-ID: <ce506a5e-5934-4149-8471-dd2da50a366c@kth.se> (raw)
In-Reply-To: <AM9PR09MB4900085829B124A0AACE3C58B4999@AM9PR09MB4900.eurprd09.prod.outlook.com>
Le 02/03/2021 à 11:26, John Alexander a écrit :
> 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?
This is not something you want as most drivers reclaim buffers in
batches for performance reasons. If you want to ensure a buffer is
reclaimed right away you would need to do some garbage collection. Most
NICs do not even ring a doorbell/update completion flags for every
transmitted packets, so you would not know when they're sent exactly
right away.
If it's lazy re-claim, I guess it's not a problem?
prev parent reply other threads:[~2021-03-02 16:22 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
2021-03-02 16:22 ` Tom Barbette [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=ce506a5e-5934-4149-8471-dd2da50a366c@kth.se \
--to=barbette@kth.se \
--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
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).