From: Stephen Hemminger <stephen@networkplumber.org>
To: Kumara Parameshwaran <kumaraparamesh92@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v3] gro : improve GRO performance based on hash table
Date: Sat, 27 Dec 2025 10:12:17 -0800 [thread overview]
Message-ID: <20251227101217.43f0f215@phoenix.local> (raw)
In-Reply-To: <20251227174221.277640-1-kumaraparamesh92@gmail.com>
On Sat, 27 Dec 2025 23:12:21 +0530
Kumara Parameshwaran <kumaraparamesh92@gmail.com> wrote:
> +static void fill_payload(char *payload, size_t len, uint8_t *ref)
> +{
> + for (size_t i = 0; i < len; i++) {
> + uint8_t val = rand() % 256;
This is a test, so security doesn't matter but DPDK has a better random number
generator than rand(). You could use rte_rand_max(UINT8_MAX) here.
prev parent reply other threads:[~2025-12-27 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 16:23 [PATCH] " Kumara Parameshwaran
2025-11-16 6:06 ` [PATCH v2] " Kumara Parameshwaran
2025-11-16 16:52 ` Stephen Hemminger
2025-12-27 17:36 ` Kumara Parameshwaran
2025-12-27 17:42 ` [PATCH v3] " Kumara Parameshwaran
2025-12-27 18:12 ` Stephen Hemminger [this message]
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=20251227101217.43f0f215@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=kumaraparamesh92@gmail.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).