From: Horst von Brand <vonbrand@sleipnir.valparaiso.cl>
To: Andreas Dilger <adilger@turbolabs.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] random.c bugfix
Date: Sun, 28 Oct 2001 20:57:02 -0300 [thread overview]
Message-ID: <200110282357.f9SNv2kD011923@sleipnir.valparaiso.cl> (raw)
In-Reply-To: Message from Andreas Dilger <adilger@turbolabs.com> of "Sat, 27 Oct 2001 00:21:42 MDT." <20011027002142.D23590@turbolinux.com>
Andreas Dilger <adilger@turbolabs.com> said:
[...]
> OK, my bad. At least the random variable-name cleanups let you SEE where
> we are supposed to be using word sizes and byte sizes. Even you were
> confused about it ;-)
I have now seen various bits and pieces about this flying around. To get it
right will be hard, as over/under estimates will show up only under unusual
circumstances; and as you _can't_ really know how much "entropy" there
should be, testing this is very hard. So the only way to get it right is
make it "obviously" right.
How hard would it be to change the API to talk _all_ in the same units, be
it bits, bytes, words, or whatever? I believe bits or bytes would be best,
as word sizes differ. Bytes have the advantage that a simple sizeof() will
give size in bytes for any random variable.
--
Horst von Brand vonbrand@sleipnir.valparaiso.cl
Casilla 9G, Vin~a del Mar, Chile +56 32 672616
next prev parent reply other threads:[~2001-10-29 0:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-27 4:21 René Scharfe
2001-10-27 6:21 ` Andreas Dilger
2001-10-28 23:57 ` Horst von Brand [this message]
2001-10-29 5:37 ` Andreas Dilger
2001-10-29 16:15 ` Horst von Brand
2001-10-29 16:58 ` Oliver Xymoron
2001-10-29 23:39 ` Andreas Dilger
2001-10-30 0:23 ` Oliver Xymoron
2001-10-30 3:50 ` Andreas Dilger
2001-10-30 16:07 ` Theodore Tso
2001-10-31 6:19 ` Andreas Dilger
2001-10-31 14:42 ` Oliver Xymoron
2001-10-30 4:49 ` Andreas Dilger
2001-10-29 5:46 ` [PATCH] MAJOR " Andreas Dilger
2001-10-27 6:35 ` [PATCH] " Robert Love
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=200110282357.f9SNv2kD011923@sleipnir.valparaiso.cl \
--to=vonbrand@sleipnir.valparaiso.cl \
--cc=adilger@turbolabs.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®