From: Robert Sanford <rsanford2@gmail.com>
To: dev@dpdk.org, cristian.dumitrescu@intel.com
Subject: [PATCH 0/4] port: fix and test bugs in tx_bulk ops
Date: Mon, 28 Mar 2016 16:51:33 -0400 [thread overview]
Message-ID: <1459198297-49854-1-git-send-email-rsanford@akamai.com> (raw)
This patch series does the following:
* enhances port ring writer test, to send two large, but not full
bursts; exposes ring writer buffer overflow
* fixes ring writer buffer overflow
* fixes full burst checks in ethdev, ring, and sched f_tx_bulk ops
* fixes ethdev writer, to send bursts no larger than specified max
--------
Robert Sanford (4):
app/test: enhance test_port_ring_writer
port: fix ring writer buffer overflow
port: fix full burst checks in f_tx_bulk ops
port: fix ethdev writer burst too big
app/test/test_table_ports.c | 27 +++++++++++++++++++++++++--
lib/librte_port/rte_port_ethdev.c | 35 ++++++++++++++---------------------
lib/librte_port/rte_port_ring.c | 20 ++++++--------------
lib/librte_port/rte_port_sched.c | 7 ++-----
4 files changed, 47 insertions(+), 42 deletions(-)
next reply other threads:[~2016-03-28 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 20:51 Robert Sanford [this message]
2016-03-28 20:51 ` [PATCH 1/4] app/test: enhance test_port_ring_writer Robert Sanford
2016-04-01 19:42 ` Sanford, Robert
2016-04-06 16:46 ` Dumitrescu, Cristian
2016-03-28 20:51 ` [PATCH 2/4] port: fix ring writer buffer overflow Robert Sanford
2016-03-31 11:21 ` Dumitrescu, Cristian
2016-03-28 20:51 ` [PATCH 3/4] port: fix full burst checks in f_tx_bulk ops Robert Sanford
2016-03-31 15:41 ` Dumitrescu, Cristian
2016-04-01 19:31 ` Sanford, Robert
2016-03-28 20:51 ` [PATCH 4/4] port: fix ethdev writer burst too big Robert Sanford
2016-03-31 13:22 ` Dumitrescu, Cristian
2016-03-30 11:00 ` [PATCH 0/4] port: fix and test bugs in tx_bulk ops Thomas Monjalon
2016-03-30 11:58 ` Dumitrescu, Cristian
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=1459198297-49854-1-git-send-email-rsanford@akamai.com \
--to=rsanford2@gmail.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.