From: Matthew Hall <mhall@mhcomputing.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC PATCH] eal: rte_rand yields only 62 random bits
Date: Fri, 27 Mar 2015 17:38:21 -0700 [thread overview]
Message-ID: <20150328003821.GA13992@mhcomputing.net> (raw)
In-Reply-To: <CAOaVG15T2v7Nq-sHUDeEtwjK17GJpQ5GZTOuLr_Q6jgECmAAoA@mail.gmail.com>
On Fri, Mar 27, 2015 at 05:03:02PM -0700, Stephen Hemminger wrote:
> I would argue remove rte_rand from DPDK.
+1
To paraphrase Donald Knuth, "Random numbers should not be generated [using a
function coded] at random."
It'd be better to fix libc, or considering that has a slow dev cycle and
platform compatibility limits, use some simple, semi-random, high-performance
BSD licensed routine from a known-good library.
Matthew.
next prev parent reply other threads:[~2015-03-28 0:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 16:18 Robert Sanford
2015-03-27 16:38 ` Sanford, Robert
2015-03-28 0:02 ` Stephen Hemminger
2015-03-28 0:03 ` Stephen Hemminger
2015-03-28 0:38 ` Matthew Hall [this message]
2015-03-30 5:28 ` Stephen Hemminger
2015-03-30 22:19 ` Robert Sanford
2015-03-31 1:51 ` Neil Horman
2015-04-01 2:17 ` 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=20150328003821.GA13992@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).