All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: Valdis.Kletnieks@vt.edu
Cc: Hubert Chan <hubert@uhoreg.ca>, reiserfs-list@namesys.com
Subject: Re: The situation at hand and in the future
Date: Wed, 09 Jun 2004 17:01:17 -0500	[thread overview]
Message-ID: <40C788AD.4000800@slaphack.com> (raw)
In-Reply-To: <200406050730.i557UouE026516@turing-police.cc.vt.edu>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Valdis.Kletnieks@vt.edu wrote:
[...]
| Proper programming would probably render encryption almost-zero overhead.
| Except for really high-end disk subsystems, you're not going to get an
*effective*
| (i.e. after seeks and rotational delay and all that) throughput of
much over
| 40 megabytes/second - and encrypting/decrypting at 40 megabytes/second

Yes, I know this.  Consider:  On Windows 9x (and 3.1, of course), when
you read from a floppy, it's unbelievably slow.  True, this doesn't
matter much when you consider how slow the physical medium is.  But
while it's actually reading it, you cannot do anything else.

So, multitasking matters.  Suppose I've got this game (because games are
fun) with two threads -- the player-kills-all thread, and the
load-rest-of-level thread.  So the player isn't going to move for awhile
- -- he's getting shot at too much -- but the game wants to load a little
more detail from disk to make the sky and/or landscape look prettier.
Without encryption, big deal -- the level-loading thread asks for the
data from the disk, then goes to sleep until it arrives, thus freeing
resources for the immediate gameplay.  With encryption, if we are trying
to load things from disk, we are also going to have to spend some CPU
decrypting them which we wouldn't otherwise.  Not much latency -- unless
you need CPU to make sure the player doesn't lag.  Or you put the thread
on a low priority, which works -- unless you need as close to 100% CPU
as possible for higher-priority threads, which drives said latency up
insanely.

Of course, most of the time people can just buy a new CPU.

Should we take this off-list?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQMeIrXgHNmZLgCUhAQJLkhAAj97ah2lvz97mmtVFvydmZ+nJPS1f/OBP
gifHHcE8ZGe/PN2Iy+1PQVz2P1GkDmk2dW8/HIid+aHYv0UZsISw6Y6rQ2Kyxr9y
OULkebG+qgV5zxwKFUMKqkTMaxFXJBQinxvf1mdEbOMmTfxW1HzKB7FYVH3muAWO
i4knab6t720m+rWQ0q+VBKKSH52CVHCno1ncZnaRiTmZlicJQ3GSitglq/5NHsk6
3PKPXM68TMWl7ms9k6Htseba3jYcW4l9kHNjHICjAbQ4hK/KYtkNhoBeTIoVcpbW
BkGa9ThKF23/3CTYNycXZ+BUS6C7RdH9iXku5WjlbrT6dlEZDDenleiJz5HEBo94
MB74xlGLpz2O/b/A/i0iie5QJyoyOzexqh+AMoJlN9n6VUS1o5sUquoDWPhL9ZvH
1BUJnm/tk9qcOuzmkcxux0sWVGambqJah9gU8F+a0AQTiT71z4UnEb78YmWfQFg7
hXsWgXG2l/aF8XKqQY4w+lZT2WsX7kcSZ417VzeoiMVx1yHpYQk2qPDC59n8EcNh
q1EmNaYJD0DEtAbexH5jZhlofB9mnpJDpRHPvixKDxvD5h7WLrcwyfJ7+SHZnykw
xUDXRumoWmF2La/Dh75SwQc6YJeyXVmOICB6uRuX7mC187wjfQfy/KC2Z6dRjNow
ysMN5rbtSLY=
=Ayvm
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2004-06-09 22:01 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 20:01 The situation at hand and in the future mjt
2004-05-27 21:05 ` Valdis.Kletnieks
2004-05-27 22:09   ` David Masover
2004-05-28  6:33     ` mjt
2004-05-28 19:53       ` Valdis.Kletnieks
2004-05-29 12:48         ` mjt
2004-05-29 14:22       ` David Masover
2004-05-29 15:49         ` mjt
2004-05-29 23:16           ` David Masover
2004-05-30  0:41             ` Hubert Chan
2004-05-30 12:29               ` mjt
2004-05-30 16:54                 ` Hubert Chan
2004-05-30 12:27             ` mjt
2004-05-30 17:09               ` Hubert Chan
2004-05-31  0:07                 ` The Amazing Dragon
2004-05-30 17:13               ` Hubert Chan
2004-05-30 18:06                 ` mjt
2004-05-31  0:45               ` David Masover
2004-05-31  8:38                 ` mjt
2004-05-31 15:12                   ` David Masover
2004-05-31 17:20                     ` Hubert Chan
2004-05-31 21:14                       ` David Masover
2004-05-31 15:16                   ` Hubert Chan
2004-06-01 13:25                 ` Edward Shushkin
2004-06-02  8:05                   ` mjt
2004-06-02 12:51                     ` Edward Shushkin
2004-06-02 15:15                       ` mjt
2004-05-31 18:31             ` Valdis.Kletnieks
2004-05-31 21:15               ` David Masover
2004-06-02  2:45           ` Hans Reiser
2004-05-29 20:04         ` Hubert Chan
2004-05-29 23:19           ` David Masover
2004-05-31 18:27             ` Valdis.Kletnieks
2004-05-31 21:23               ` David Masover
2004-06-01  2:09                 ` Hubert Chan
2004-06-05  4:50                   ` David Masover
2004-06-05  7:30                     ` Valdis.Kletnieks
2004-06-05 10:07                       ` Christian Iversen
2004-06-07 17:35                         ` Valdis.Kletnieks
2004-06-09 22:01                       ` David Masover [this message]
2004-06-10  8:23                         ` mjt

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=40C788AD.4000800@slaphack.com \
    --to=ninja@slaphack.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=hubert@uhoreg.ca \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.