From: Philipp B <philippb.ontour@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] rte_eth_tx_burst: Can I insert timing gaps
Date: Thu, 11 Oct 2018 11:03:55 +0200 [thread overview]
Message-ID: <CAGaw3Zn3E8bO37BTVbyaLwrPoTnW9a=rSJb+5GNL-9AZda10XQ@mail.gmail.com> (raw)
Hi all!
I am working on an RTP test traffic generator. The basic idea is
clock_nanosleep providing a 20ms clock cycle to start a (big) number
of rte_eth_tx_bursts, sending equally sized buffers. As long as the
timing within a 20ms cycle is dictated primarily by the line speed, I
can be sure that not just the first buffer of each cycle has a period
of 20ms, but also the n-th buffer. (I have sent n-1 buffers before
with the same size.)
Basically, I see one 20ms interval as a series of time slots, each
capable to store an active RTP stream. My question now is, what to to
with inactive time slots? As long as all active streams are located at
consecutive time slots from the start of the 20ms interval, everything
is fine. But I cannot guarantee this.
What I need is some kind of dummy buffer, which is not transmitted but
generates a tx timing gap as a buffer of X bytes would take to be
transferred.
Is such a functionality provided? As a workaround, I already thought
about sending invalid packets (bad IP Header checksum?). However, this
won't be optimal when multiple lines are aggregated.
Thanks!
Philipp Beyer
next reply other threads:[~2018-10-11 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 9:03 Philipp B [this message]
2018-10-13 21:05 ` Cliff Burdick
2018-10-15 10:44 ` Philipp B
2018-10-15 11:20 ` Andrew Bainbridge
2018-10-15 14:29 ` Cliff Burdick
2018-10-15 16:14 ` Andrew Bainbridge
[not found] ` <24D5A228-47D5-4FEE-9DD4-A6CFBAFC3EB5@net.in.tum.de>
2018-10-16 13:15 ` Philipp B
2018-10-15 11:54 ` 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='CAGaw3Zn3E8bO37BTVbyaLwrPoTnW9a=rSJb+5GNL-9AZda10XQ@mail.gmail.com' \
--to=philippb.ontour@gmail.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).