From: Stephen Hemminger <stephen@networkplumber.org>
To: Konstantin Ananyev <konstantin.ananyev@huawei.com>
Cc: "Mattias Rönnblom" <hofors@lysator.liu.se>,
"dev@dpdk.org" <dev@dpdk.org>,
"Morten Brørup" <mb@smartsharesystems.com>,
"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>
Subject: Re: [PATCH v2] eal: allow setting random number generator seed
Date: Mon, 14 Sep 2026 09:47:47 -0700 [thread overview]
Message-ID: <20260914094747.6a96a587@phoenix.local> (raw)
In-Reply-To: <8bf95eb0e0704401a1168a4e4fd238de@huawei.com>
On Mon, 14 Sep 2026 12:04:16 +0000
Konstantin Ananyev <konstantin.ananyev@huawei.com> wrote:
> >
> > Provided the test results depend on something that use the PRNG before
> > the test driver has had the opportunity to call rte_srand(), controlling
> > the *initial* seed may be required.
> >
> > I don't think this feature should be controlled by an environment
> > variable. There is no precedent for that. If this functionality is
> > deemed useful, it should be an EAL command line option, it seems to me.
>
> +1
I thought about that but getting command line options into EAL when
using meson test runner is awkward (not impossible though).
next prev parent reply other threads:[~2026-09-14 16:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 22:58 [RFC] eal: allow setting random number generator seed Stephen Hemminger
2026-09-12 6:26 ` Morten Brørup
2026-09-12 16:16 ` [PATCH v2] " Stephen Hemminger
2026-09-14 11:29 ` Mattias Rönnblom
2026-09-14 12:04 ` Konstantin Ananyev
2026-09-14 16:47 ` Stephen Hemminger [this message]
2026-09-14 16:46 ` Stephen Hemminger
2026-09-14 9:05 ` [RFC] " Marat Khalili
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=20260914094747.6a96a587@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=hofors@lysator.liu.se \
--cc=konstantin.ananyev@huawei.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=mb@smartsharesystems.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 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.