From: Rik van Riel <riel@conectiva.com.br>
To: Ted Unangst <tedu@Stanford.EDU>
Cc: linux-mm@kvack.org
Subject: Re: help for swap encryption
Date: Thu, 16 Aug 2001 23:09:37 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0108162307290.5646-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <Pine.GSO.4.31.0108161312050.29454-100000@cardinal0.Stanford.EDU>
On Thu, 16 Aug 2001, Ted Unangst wrote:
> 1. the data is at page->virtual, right? that's what i want.
Doing this will make your scheme unable to work on
machines with more than 890MB of RAM.
> 2. if a page gets written to disk, nobody will be trying to read the
> former RAM location, correct? i was going to encrypt the ram in place.
> nobody is going to go back and try reading that RAM again, are they?
Wrong. You'll have to remove the page from the swap
cache first, possibly moving it to an encrypted
swap cache ;)
> 3. when a page is pulled off disk, it's not automatically deleted.
> when does that occur?
It only occurs when swap space is getting full and
is done in do_swap_page().
> 4. i don't know much about kernel programming style. would it be
> better to store tables of data as static variables, or kmalloc a big
> chunk at some point?
Using static variables you'd make your algorithm
unable to run on multiple CPUs at the same time on
an SMP system and is cause for instant disqualification.
regards,
Rik
--
IA64: a worthy successor to i860.
http://www.surriel.com/ http://distro.conectiva.com/
Send all your spam to aardvark@nl.linux.org (spam digging piggy)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next parent reply other threads:[~2001-08-17 2:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.GSO.4.31.0108161312050.29454-100000@cardinal0.Stanford.EDU>
2001-08-17 2:09 ` Rik van Riel [this message]
2001-08-17 3:37 ` Ted Unangst
2001-08-18 17:53 ` Ingo Oeser
2001-08-18 22:22 ` Ted Unangst
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=Pine.LNX.4.33L.0108162307290.5646-100000@imladris.rielhome.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-mm@kvack.org \
--cc=tedu@Stanford.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