From: Rafal Kozik <rk@semihalf.com>
To: dev@dpdk.org, keith.wiles@intel.com
Cc: mw@semihalf.com, mk@semihalf.com, gtzalik@amazon.com,
evgenys@amazon.com, matua@amazon.com, igorch@amazon.com,
Rafal Kozik <rk@semihalf.com>
Subject: [dpdk-dev] [PATCH 0/5][pktgen] fixes and minor features
Date: Thu, 10 Jan 2019 17:14:01 +0100 [thread overview]
Message-ID: <1547136846-23319-1-git-send-email-rk@semihalf.com> (raw)
Hello Keith,
This patch set contain two fixes for issues that were noticed when running
DPDK in debug configuration. There are also three minor features that
may be useful. Those patches are independent from each other.
I am kindly asking, if those changes are appropriate
to be merged to Pktgen?
Best regards,
Rafal
Rafal Kozik (5):
[pktgen] fix race condition in start
[pktgen] different PCAP per each queue
[pktgen] use constants for PCAP creation
[pktgen] expose number of missed Rx packets
[pktgen] fix cleanup of not sent packets
app/lpktgenlib.c | 1 +
app/pktgen-cmds.c | 4 ++--
app/pktgen-main.c | 40 ++++++++++++++++++++++++++++++----------
app/pktgen-pcap.c | 34 +++++++++++++++++-----------------
app/pktgen-port-cfg.c | 8 +++++++-
app/pktgen-port-cfg.h | 1 +
app/pktgen.c | 7 +++----
7 files changed, 61 insertions(+), 34 deletions(-)
--
2.7.4
next reply other threads:[~2019-01-10 16:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 16:14 Rafal Kozik [this message]
2019-01-10 16:14 ` [dpdk-dev] [PATCH 1/5] [pktgen] fix race condition in start Rafal Kozik
2019-01-10 16:14 ` [dpdk-dev] [PATCH 2/5] [pktgen] different PCAP per each queue Rafal Kozik
2019-01-10 16:14 ` [dpdk-dev] [PATCH 3/5] [pktgen] use constants for PCAP creation Rafal Kozik
2019-01-10 16:14 ` [dpdk-dev] [PATCH 4/5] [pktgen] expose number of missed Rx packets Rafal Kozik
2019-01-10 16:14 ` [dpdk-dev] [PATCH 5/5] [pktgen] fix cleanup of not sent packets Rafal Kozik
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=1547136846-23319-1-git-send-email-rk@semihalf.com \
--to=rk@semihalf.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=gtzalik@amazon.com \
--cc=igorch@amazon.com \
--cc=keith.wiles@intel.com \
--cc=matua@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
/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).