From: Andrew Clausen <clausen@gnu.org>
To: reiserfs-list@namesys.com
Cc: Peter Foldiak <Peter.Foldiak@st-andrews.ac.uk>
Subject: Re: secure delete?
Date: Sun, 21 Mar 2004 10:59:37 +1100 [thread overview]
Message-ID: <20040320235937.GB572@gnu.org> (raw)
In-Reply-To: <200403202345.i2KNj8VK024070@sirius.cs.pdx.edu>
On Sat, Mar 20, 2004 at 03:45:08PM -0800, The Amazing Dragon wrote:
> > I guess you would have to use an encrypted swap area as well, right?
> > Would the performance be ok for that? Peter
>
> How many orders of magnitude are disks slower than processors/memory?
> Encryption algorithms are designed to be fast to compute. Even the
> slowest processors of today will be able to encrypt/descrypt data much
> faster than the maximum throughput of hard disks. With swap you're going
> to be drowned by seeks anyway.
I don't think this is relevant. The question probably wasn't "how much
will it slow down swap read/writes" but rather "how much will it slow
down my system in general".
You may be correct in observing that encryption/decryption won't make a
big difference in the latency on swap I/O. (If you are getting a good
stream out of a hard disk, it might be hard for crypto to keep up, but
this is unlikely for swap) However, it still may significantly increase
CPU usage, and hence reduce the amount of CPU available to other
processes (that aren't waiting for swap I/O). It's not like I/O in
Linux is synchronous!
Cheers,
Andrew
next prev parent reply other threads:[~2004-03-20 23:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 10:13 secure delete? Peter Foldiak
2004-03-19 11:01 ` Cami
[not found] ` <20040319110748.GA30491@chihiro.cern.ch>
2004-03-19 11:29 ` Hans Reiser
2004-03-19 11:51 ` Peter Foldiak
2004-03-19 16:04 ` Hubert Chan
2004-03-19 17:54 ` Bennett Todd
2004-03-20 23:45 ` The Amazing Dragon
2004-03-20 23:59 ` Andrew Clausen [this message]
2004-03-23 1:37 ` Jurgen Botz
2004-03-23 2:49 ` Valdis.Kletnieks
2004-03-23 6:22 ` Hans Reiser
2004-03-23 6:40 ` Hendrik Visage
2004-03-23 16:34 ` Jürgen Botz
2004-03-23 21:03 ` Jason Holt
2004-03-23 21:40 ` Hans Reiser
2004-03-24 2:36 ` Tom Vier
2004-03-24 6:26 ` Jason Holt
2004-03-24 7:39 ` Hans Reiser
2004-03-24 15:38 ` Jason Holt
2004-03-29 12:59 ` Hans Reiser
2004-03-24 7:54 ` Hans Reiser
2004-03-24 8:04 ` Vladimir Saveliev
2004-03-24 23:18 ` Enrique Perez-Terron
2004-03-25 3:49 ` Tom Vier
2004-03-25 13:00 ` Vladimir Saveliev
2004-03-24 18:20 ` Valdis.Kletnieks
2004-03-25 3:16 ` Tom Vier
2004-03-30 1:10 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2004-03-30 2:13 Burnes, James
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=20040320235937.GB572@gnu.org \
--to=clausen@gnu.org \
--cc=Peter.Foldiak@st-andrews.ac.uk \
--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.