From: Andi Kleen <andi@firstfloor.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Andi Kleen <andi@firstfloor.org>,
Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>,
netdev@vger.kernel.org
Subject: Re: [PATCH] Stochastic Fair Blue queue discipline
Date: Thu, 10 Apr 2008 09:36:52 +0200 [thread overview]
Message-ID: <20080410073652.GC10019@one.firstfloor.org> (raw)
In-Reply-To: <47FD6C0E.7040808@trash.net>
> Well, if I'm not mistaken net_random() used to be a function
> (in net/core/utils.c) that didn't have this problem.
Correct it's a regression.
> So these
> problems seem to have been introduced by the conversion to
> srandom().
I think the per CPU ness was generally a mistake, it was a misguided
optimization and hurts
Iff someone really needs per cpu RNDs the better way would have been
to add a rand_r() like interface with explicit state and only do
that in that particular caller.
Also I think a lot of get_random_bytes() shouldn't really be using it
because they don't need precious cryptographically strong entropy,
but rather should get their data from another RND which has been
seeded once from the entropy pool only.
-Andi
next prev parent reply other threads:[~2008-04-10 7:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 22:37 [PATCH] Stochastic Fair Blue queue discipline Juliusz Chroboczek
2008-04-08 0:04 ` Patrick McHardy
2008-04-08 0:56 ` Patrick McHardy
2008-04-08 15:28 ` Juliusz Chroboczek
2008-04-08 8:20 ` Andi Kleen
2008-04-08 12:11 ` Patrick McHardy
2008-04-08 15:39 ` Juliusz Chroboczek
2008-04-08 15:45 ` Patrick McHardy
2008-04-09 15:48 ` Juliusz Chroboczek
2008-04-09 16:00 ` Patrick McHardy
2008-04-08 15:38 ` Juliusz Chroboczek
2008-04-08 16:32 ` Andi Kleen
2008-04-08 17:35 ` Juliusz Chroboczek
2008-04-08 17:53 ` Andi Kleen
2008-04-09 15:45 ` Juliusz Chroboczek
2008-04-09 17:49 ` Andi Kleen
2008-04-10 1:23 ` Patrick McHardy
2008-04-10 1:38 ` Patrick McHardy
2008-04-10 11:17 ` Juliusz Chroboczek
2008-04-11 13:07 ` Patrick McHardy
2008-04-10 14:04 ` Stephen Hemminger
2008-04-10 7:36 ` Andi Kleen [this message]
2008-04-08 16:44 ` Patrick McHardy
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=20080410073652.GC10019@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=Juliusz.Chroboczek@pps.jussieu.fr \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.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).