From: "jonathan.ribas@fraudbuster.mobi" <jonathan.ribas@fraudbuster.mobi>
To: announce@dpdk.org
Subject: [dpdk-announce] New DPDK hosted project: dpdk-burst-replay
Date: Thu, 31 Jan 2019 14:10:48 +0100 [thread overview]
Message-ID: <dd982110-32fe-8226-1f91-bd85b2c47034@fraudbuster.mobi> (raw)
Hello all,
A new project has come into the DPDK community, a tiny tool
named "dpdk-burst-replay" whitch tend to be a "tcpreplay" like
based on DPDK (so, with high performance concerns).
ATM, only few features are available:
- it can replay a pcap multiple times in a row.
- it can replay a pcap on multiple NIC ports.
- and it replay the pcap at maximum bitrate, by pre-caching
the dump before starting to send packets.
- and at the end, it gave some statistics.
The main tool's objectives are to be simple (it manages itself
all the EAL/mempool/port initialization etc) and to be as fast
as possible.
You can have a look on the README here:
https://doc.dpdk.org/burst-replay/readme.html
And at the source code here:
http://git.dpdk.org/apps/dpdk-burst-replay/
Finally, to fill an issue, use the dedicated bugzilla:
https://bugs.dpdk.org/enter_bug.cgi?product=dpdk-burst-replay
A presentation will be made at FOSDEM this Saturday, for those
who are interested and can't be there, it will be recorded and
should be available next week here:
https://fosdem.org/2019/schedule/event/dpdk_burst_replay/
Do not hesitate to give me feedback!
NB: This tool is released under BSD 3-clause license. All
contributions will be welcomed! :)
Regards,
Jonathan.
reply other threads:[~2019-01-31 13:10 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=dd982110-32fe-8226-1f91-bd85b2c47034@fraudbuster.mobi \
--to=jonathan.ribas@fraudbuster.mobi \
--cc=announce@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).