From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Ammar Faizi <[email protected]>,
io_uring Mailing List <[email protected]>
Subject: [PATCH liburing v2 0/2] Fix endianess issue and add srand()
Date: Mon, 27 Sep 2021 20:40:21 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, Sep 27, 2021 at 8:28 PM Jens Axboe <[email protected]> wrote:
>
> On 9/26/21 10:37 PM, Ammar Faizi wrote:
> > The use of `rand()` should be accompanied by `srand()`.
>
> The idiomatic way that I usually do it for these tests is:
>
> srand(getpid());
>
> Shouldn't really matter, but we may as well keep it consistent.
v2: Use getpid() for the random seed.
----------------------------------------------------------------
Ammar Faizi (2):
test: Fix endianess issue on `bind()` and `connect()`
test/accept-link: Add `srand()` for better randomness
test/232c93d07b74-test.c | 9 +++++----
test/accept-link.c | 14 ++++++++++----
test/accept.c | 5 +++--
test/poll-link.c | 11 +++++++----
test/shutdown.c | 5 +++--
test/socket-rw-eagain.c | 5 +++--
test/socket-rw.c | 5 +++--
7 files changed, 34 insertions(+), 20 deletions(-)
---
Ammar Faizi
next prev parent reply other threads:[~2021-09-27 13:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 4:37 [PATCH liburing 0/2] Fix endianess issue and add srand() Ammar Faizi
2021-09-27 4:37 ` [PATCH liburing 1/2] test: Fix endianess issue on `bind()` and `connect()` Ammar Faizi
2021-09-27 4:37 ` [PATCH liburing 2/2] test/accept-link: Add `srand()` for better randomness Ammar Faizi
2021-09-27 13:28 ` Jens Axboe
2021-09-27 13:40 ` Ammar Faizi [this message]
2021-09-27 13:40 ` [PATCH liburing v2 1/2] test: Fix endianess issue on `bind()` and `connect()` Ammar Faizi
2021-09-27 13:40 ` [PATCH liburing v2 2/2] test/accept-link: Add `srand()` for better randomness Ammar Faizi
2021-09-27 13:45 ` [PATCH liburing v2 0/2] Fix endianess issue and add srand() Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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