From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v3 2/3] test: allow larger packet sizes
Date: Thu, 8 Jan 2026 12:40:47 -0800 [thread overview]
Message-ID: <20260108204449.176087-3-stephen@networkplumber.org> (raw)
In-Reply-To: <20260108204449.176087-1-stephen@networkplumber.org>
The packet length in packet burst generator was uint8_t which
limited usefulness for testing larger packet sizes.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
app/test/packet_burst_generator.c | 30 ++++++++++++++++++++----------
app/test/packet_burst_generator.h | 4 ++--
2 files changed, 22 insertions(+), 12 deletions(-)
diff --git a/app/test/packet_burst_generator.c b/app/test/packet_burst_generator.c
index 4c17737739..4f659e4d71 100644
--- a/app/test/packet_burst_generator.c
+++ b/app/test/packet_burst_generator.c
@@ -216,13 +216,18 @@ int
generate_packet_burst(struct rte_mempool *mp, struct rte_mbuf **pkts_burst,
struct rte_ether_hdr *eth_hdr, uint8_t vlan_enabled,
void *ip_hdr, uint8_t ipv4, struct rte_udp_hdr *udp_hdr,
- int nb_pkt_per_burst, uint8_t pkt_len, uint8_t nb_pkt_segs)
+ int nb_pkt_per_burst, uint16_t pkt_len, uint8_t nb_pkt_segs)
{
- const uint8_t pkt_seg_data_len = pkt_len / nb_pkt_segs;
+ int i, nb_pkt = 0;
+ size_t eth_hdr_size;
struct rte_mbuf *pkt_seg;
struct rte_mbuf *pkt;
- size_t eth_hdr_size;
- int i, nb_pkt = 0;
+ uint16_t pkt_seg_data_len;
+ uint16_t last_seg_data_len;
+
+ /* Calculate per-segment data length */
+ pkt_seg_data_len = pkt_len / nb_pkt_segs;
+ last_seg_data_len = pkt_seg_data_len + (pkt_len % nb_pkt_segs);
for (nb_pkt = 0; nb_pkt < nb_pkt_per_burst; nb_pkt++) {
pkt = rte_pktmbuf_alloc(mp);
@@ -246,7 +251,7 @@ generate_packet_burst(struct rte_mempool *mp, struct rte_mbuf **pkts_burst,
if (i != nb_pkt_segs - 1)
pkt_seg->data_len = pkt_seg_data_len;
else
- pkt_seg->data_len = pkt_seg_data_len + pkt_len % nb_pkt_segs;
+ pkt_seg->data_len = last_seg_data_len;
}
pkt_seg->next = NULL; /* Last segment of packet. */
@@ -300,13 +305,18 @@ generate_packet_burst_proto(struct rte_mempool *mp,
struct rte_mbuf **pkts_burst, struct rte_ether_hdr *eth_hdr,
uint8_t vlan_enabled, void *ip_hdr,
uint8_t ipv4, uint8_t proto, void *proto_hdr,
- int nb_pkt_per_burst, uint8_t pkt_len, uint8_t nb_pkt_segs)
+ int nb_pkt_per_burst, uint16_t pkt_len, uint8_t nb_pkt_segs)
{
- const uint8_t pkt_seg_data_len = pkt_len / nb_pkt_segs;
+ int i, nb_pkt = 0;
+ size_t eth_hdr_size;
struct rte_mbuf *pkt_seg;
struct rte_mbuf *pkt;
- size_t eth_hdr_size;
- int i, nb_pkt = 0;
+ uint16_t pkt_seg_data_len;
+ uint16_t last_seg_data_len;
+
+ /* Calculate per-segment data length */
+ pkt_seg_data_len = pkt_len / nb_pkt_segs;
+ last_seg_data_len = pkt_seg_data_len + (pkt_len % nb_pkt_segs);
for (nb_pkt = 0; nb_pkt < nb_pkt_per_burst; nb_pkt++) {
pkt = rte_pktmbuf_alloc(mp);
@@ -330,7 +340,7 @@ generate_packet_burst_proto(struct rte_mempool *mp,
if (i != nb_pkt_segs - 1)
pkt_seg->data_len = pkt_seg_data_len;
else
- pkt_seg->data_len = pkt_seg_data_len + pkt_len % nb_pkt_segs;
+ pkt_seg->data_len = last_seg_data_len;
}
pkt_seg->next = NULL; /* Last segment of packet. */
diff --git a/app/test/packet_burst_generator.h b/app/test/packet_burst_generator.h
index cce41bcd0f..600addee3a 100644
--- a/app/test/packet_burst_generator.h
+++ b/app/test/packet_burst_generator.h
@@ -62,14 +62,14 @@ int
generate_packet_burst(struct rte_mempool *mp, struct rte_mbuf **pkts_burst,
struct rte_ether_hdr *eth_hdr, uint8_t vlan_enabled,
void *ip_hdr, uint8_t ipv4, struct rte_udp_hdr *udp_hdr,
- int nb_pkt_per_burst, uint8_t pkt_len, uint8_t nb_pkt_segs);
+ int nb_pkt_per_burst, uint16_t pkt_len, uint8_t nb_pkt_segs);
int
generate_packet_burst_proto(struct rte_mempool *mp,
struct rte_mbuf **pkts_burst, struct rte_ether_hdr *eth_hdr,
uint8_t vlan_enabled, void *ip_hdr,
uint8_t ipv4, uint8_t proto, void *proto_hdr,
- int nb_pkt_per_burst, uint8_t pkt_len, uint8_t nb_pkt_segs);
+ int nb_pkt_per_burst, uint16_t pkt_len, uint8_t nb_pkt_segs);
#ifdef __cplusplus
}
--
2.51.0
next prev parent reply other threads:[~2026-01-08 20:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-04 22:25 [PATCH] test: add a test for null PMD Stephen Hemminger
2026-01-05 14:49 ` Marat Khalili
2026-01-05 17:38 ` Stephen Hemminger
2026-01-06 16:47 ` [PATCH v2 0/2] net/null: add a test Stephen Hemminger
2026-01-06 16:47 ` [PATCH v2 1/2] test: add a test for null PMD Stephen Hemminger
2026-01-06 17:40 ` Marat Khalili
2026-01-06 18:01 ` Stephen Hemminger
2026-01-06 16:47 ` [PATCH v2 2/2] net/null: revise info_get Stephen Hemminger
2026-01-08 20:40 ` [PATCH v3 0/3] test: new test for null PMD Stephen Hemminger
2026-01-08 20:40 ` [PATCH v3 1/3] net/null: cleanup info_get Stephen Hemminger
2026-01-08 20:40 ` Stephen Hemminger [this message]
2026-01-09 15:00 ` [PATCH v3 2/3] test: allow larger packet sizes Morten Brørup
2026-01-10 17:21 ` Stephen Hemminger
2026-01-08 20:40 ` [PATCH v3 3/3] test: add a test for null PMD Stephen Hemminger
2026-01-09 1:21 ` Stephen Hemminger
2026-01-10 17:22 ` [PATCH v4 0/3] null pmd minor cleanup and add test Stephen Hemminger
2026-01-10 17:22 ` [PATCH v4 1/3] net/null: cleanup info_get Stephen Hemminger
2026-01-10 17:22 ` [PATCH v4 2/3] test: generate larger packet bursts Stephen Hemminger
2026-01-10 17:22 ` [PATCH v4 3/3] test: add a test for null PMD Stephen Hemminger
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=20260108204449.176087-3-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--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 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).