From: sama@aglorioso.com
To: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] FW: proposal for systems that do not require security
Date: Tue, 10 Apr 2001 16:28:45 +0200 [thread overview]
Message-ID: <20010410162845.A18276@aglorioso.com> (raw)
In-Reply-To: <27525795B28BD311B28D00500481B7601F11A6@ftrs1.intranet.ftr.nl>
In-Reply-To: <27525795B28BD311B28D00500481B7601F11A6@ftrs1.intranet.ftr.nl>; from f.v.heusden@ftr.nl on Tue, Apr 10, 2001 at 02:35:52PM +0200
On Tue, Apr 10, 2001 at 02:35:52PM +0200, Heusden, Folkert van wrote:
> Hi,
>
> I have an idea: I have a couple of linux-systems running in a intranet which
> is not connected to do outside world in any way. Since they're only used for
> calculations for which there is no harm if anyone would tamper with them,
> security is not neccessary. The only thing important, is performance. Huge
> amounts of data must be transferred inbetween these boxes.
> So, I was wondering: isn't it a nice idea to have a switch in the
> configuration menu to disable entropy-gathering in the interrupt-routines,
> have some simplistic routine (like x'=(x * m + a) % p) which returns a non-
> cryptographic value, and something similar symplistic for the network-
> traffic routines?
Have you already tried to measure how much impact has entropy
gathering on the overall performances? Something like the Linux Trace
Toolkit (http://www.opersys.com/LTT/) could be of help here.
I doubt such optimization is useful to the mainstream kernel tree,
but it would be interesting to compare numbers nonetheless.
Ciao,
Andrea Glorioso
next prev parent reply other threads:[~2001-04-10 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-10 12:35 [RFC] FW: proposal for systems that do not require security Heusden, Folkert van
2001-04-10 13:11 ` Andrey Panin
2001-04-10 14:28 ` sama [this message]
2001-04-20 9:02 ` Jeremy Fitzhardinge
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 13:16 Heusden, Folkert van
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=20010410162845.A18276@aglorioso.com \
--to=sama@aglorioso.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