From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 276] rte_rand() bit 31 and 63 are always zero
Date: Mon, 06 May 2019 13:00:47 +0000 [thread overview]
Message-ID: <bug-276-3@http.bugs.dpdk.org/> (raw)
Message-ID: <20190506130047.XvLiYaUBSnVtNenTSY09jdELcY9en-p_KIFftdhGmpM@z> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=276
Bug ID: 276
Summary: rte_rand() bit 31 and 63 are always zero
Product: DPDK
Version: 19.05
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: mattias.ronnblom@ericsson.com
Target Milestone: ---
rte_rand() is specified as returning a 64-bit pseudo-random number, but only
returns 62 bit worth of randomness.
The implementation uses two lrand48() calls, which each returns a 31-bit random
number. This results in bit 31 and 63 always being zero.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-05-06 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 13:00 bugzilla [this message]
2019-05-06 13:00 ` bugzilla
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=bug-276-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.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).