From: Philipp Beyer <pbeyer@voipfuture.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Beginners question: rte_eth_tx_burst, rte_mbuf access synchronization
Date: Fri, 11 Nov 2016 14:09:59 +0100 [thread overview]
Message-ID: <cbdda5d5-4ca4-7b9a-f33e-a95653c937f0@voipfuture.com> (raw)
In-Reply-To: <CAEXHiZFbVifG7neZg1uTZdFxxWGPZC-hqJBCZt4=2MOZVyP81w@mail.gmail.com>
Hi Anupam,
I'm afraid, I don't get your point. rte_eth_tx_burst returning a
reduced buffer count means that TX queue is filled up, doesn't it? I
don't see why "buffer M does not fit into TX queue" means "buffers 1..N
already transmitted".
Thanks,
Philipp
Am 11.11.2016 um 13:35 schrieb Anupam Kapoor:
>
> On Fri, Nov 11, 2016 at 3:19 PM, Philipp Beyer <pbeyer@voipfuture.com
> <mailto:pbeyer@voipfuture.com>> wrote:
>
> Basically, I need to send the same packet over a single interface,
> over an over again, with single bytes changed each time.
> I use rte_eth_tx_burst to send 16 packets at once. As I want to
> re-use the same buffers in a very simple way, I just increment the
> refcnt
> accordingly.
>
>
> just throwing it out there: have you considered a trivial scheme of
> repeatedly invoking 'rte_eth_tx_burst(...)' till a value less than
> 'nb_pkts' is returned. once you reach that state, then the reuse can
> happen...
>
> --
> kind regards
> anupam
>
>
> In the beginning was the lambda, and the lambda was with Emacs, and
> Emacs was the lambda.
next prev parent reply other threads:[~2016-11-11 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 9:49 Philipp Beyer
2016-11-11 12:35 ` Anupam Kapoor
2016-11-11 13:09 ` Philipp Beyer [this message]
2016-11-11 13:45 ` Matt Laswell
2016-11-11 14:06 ` Philipp Beyer
[not found] ` <9754A038-DB66-417F-8958-2DDDE317E7A2@net.in.tum.de>
2016-11-11 14:16 ` Paul Emmerich
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=cbdda5d5-4ca4-7b9a-f33e-a95653c937f0@voipfuture.com \
--to=pbeyer@voipfuture.com \
--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).