From: Stephen Hemminger <shemminger@vyatta.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Matt Mackall <mpm@selenic.com>, Jack Steiner <steiner@sgi.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] - Randomize node rotor used in cpuset_mem_spread_node()
Date: Wed, 28 Apr 2010 16:22:46 -0700 [thread overview]
Message-ID: <20100428162246.7e4632dc@nehalam> (raw)
In-Reply-To: <20100428161244.5d351395.akpm@linux-foundation.org>
On Wed, 28 Apr 2010 16:12:44 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 28 Apr 2010 18:04:06 -0500
> Matt Mackall <mpm@selenic.com> wrote:
>
> > > I suspect random32() would suffice here. It avoids depleting the
> > > entropy pool altogether.
> >
> > I wouldn't worry about that. get_random_int() touches the urandom pool,
> > which will always leave entropy around. Also, Ted and I decided over a
> > year ago that we should drop the whole entropy accounting framework,
> > which I'll get around to some rainy weekend.
>
> hm, so why does random32() exist? Speed?
Because I need a cheap fast pseudo-random source for emulation
and it got used for more and more non-cryptographic uses.
And like most random generators people keep forgetting that
it was not intended for security use.
--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-04-28 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 13:12 [PATCH] - Randomize node rotor used in cpuset_mem_spread_node() Jack Steiner
2010-04-28 15:04 ` [PATCH v2] " Jack Steiner
2010-04-28 22:40 ` Andrew Morton
2010-04-28 23:04 ` Matt Mackall
2010-04-28 23:12 ` Andrew Morton
2010-04-28 23:22 ` Stephen Hemminger [this message]
2010-04-28 23:28 ` Matt Mackall
2010-04-29 3:57 ` Robin Holt
2010-04-29 20:08 ` Jack Steiner
2010-04-29 20:09 ` [PATCH v3] " Jack Steiner
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=20100428162246.7e4632dc@nehalam \
--to=shemminger@vyatta.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=steiner@sgi.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).