From: Andrey Utkin <andrey.krieger.utkin@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
hannes@stressinduktion.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Reading large amounts from /dev/urandom broken
Date: Sun, 10 Aug 2014 14:51:08 +0300 [thread overview]
Message-ID: <CANZNk83jWeqkESFVVNb4KS+H6gQYgcVtcU8xEMiMHz7jfE52nQ@mail.gmail.com> (raw)
In-Reply-To: <20140809074539.GA1467@amd.pavel.ucw.cz>
2014-08-09 10:45 GMT+03:00 Pavel Machek <pavel@ucw.cz>:
> Warn about my quick benchmark?
>
> http://atrey.karlin.mff.cuni.cz/~pavel/quickbench.html
>
> I don't see what is insane about it. Yes, there might be more
> effective generators of random bits, but that is not the point, this
> is quick&dirty attempt at benchmark.
>
> Also people will use cat /dev/urandom > /dev/sdX (and similar) to
> clean hard drives. There should be no need to warn about
> that. (Performance is going to be disk-limited anyway).
I believe "cat /dev/urandom" doesn't result in reading with _block
size_ more than 32 MB. As it was already explained by Theodore,
currently single read() operation will return "short read" when
requested to give more than 32 MB at once. You still can read more in
consecuential reading acts.
--
Andrey Utkin
next prev parent reply other threads:[~2014-08-10 11:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 13:52 Reading large amounts from /dev/urandom broken Andrey Utkin
2014-07-23 14:32 ` Hannes Frederic Sowa
2014-07-23 15:14 ` Theodore Ts'o
2014-07-23 15:19 ` Hannes Frederic Sowa
2014-07-24 20:39 ` Alex Elsayed
2014-08-09 7:45 ` Pavel Machek
2014-08-10 11:51 ` Andrey Utkin [this message]
2014-08-12 9:14 ` Pavel Machek
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=CANZNk83jWeqkESFVVNb4KS+H6gQYgcVtcU8xEMiMHz7jfE52nQ@mail.gmail.com \
--to=andrey.krieger.utkin@gmail.com \
--cc=hannes@stressinduktion.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tytso@mit.edu \
/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).