From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Hybrid drives
Date: Sat, 17 Jul 2010 13:45:34 +0200 [thread overview]
Message-ID: <20100717114534.GA8906@fancy-poultry.org> (raw)
In-Reply-To: <1279364748.28285.5.camel@phantom.hip>
On 17.07.2010, Mikko Rauhala wrote:
> > When you format the disc using "cryptsetup luksFormat", the 4 GB SSD part
> > isn't included. Please correct me if I'm wrong.
> You're wrong in a very confused way. The SSD never stores anything that
> wasn't on the hard disk, and only a part of that anyway. All operations
> on the disk likewise indirectly affect the SSD cache.
It's quite clear to me how the crypto layer works, and data send /written
to the SSD cache only gets there in encrypted form when the SSD part is
used as a disc cache exclusively. I'm not quite good in explaining things,
I guess :-) I'm just curious if this SSD part is "just a cache", or maybe
something else, as e.g. an additional "drive" with its one device, or a
mixture of that... That wasn't quite clear to me. There's some articles
out there which describe this SSD part as a "cache only" area, just like
the cache which commonly is used with any harddisc drive, and I've read a
report which described this area as a kind of "additional drive" which
gets used as a cache at the same time, just if you would store your linux
swap on an extra harddisk.
Don't know if you can follow me now, blame it on me in this case, thinking
"'round the corner" :-)
next prev parent reply other threads:[~2010-07-17 11:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 7:13 [dm-crypt] Hybrid drives Heinz Diehl
2010-07-17 7:17 ` Heinz Diehl
2010-07-17 7:58 ` Luca Berra
2010-07-17 9:46 ` Heinz Diehl
2010-07-17 11:05 ` Mikko Rauhala
2010-07-17 11:45 ` Heinz Diehl [this message]
2010-07-17 13:27 ` Sven Eschenberg
2010-07-17 11:10 ` Christoph Anton Mitterer
2010-07-17 10:57 ` Christoph Anton Mitterer
2010-07-18 17:01 ` Arno Wagner
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=20100717114534.GA8906@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=dm-crypt@saout.de \
/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