From: Vlad Harchev <hvv@hippo.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4 and cryptofs on raid1 - what will be cached and how many times
Date: Mon, 3 Mar 2003 13:38:32 +0400 [thread overview]
Message-ID: <20030303093832.GA4601@h> (raw)
In-Reply-To: <20030302105634.GA4258@h>
On Sun, Mar 02, 2003 at 02:56:34PM +0400, Vlad Harchev wrote:
> Hello,
>
> Could you please answer the following question:
>
> Suppose we have a crypto filesystem on a raid1 array of 2 devices. What will
> the kernel cache of fileystem data contain - encrypted data or not? Will is
> be 2 copies of the same data in the cache or not?
Sorry for confusion - of course I meant linux software raid here..
> Is there any way to force kernel to cache the same file data only once, and
> keep it unencrypted (in cache)?
>
--
Best regards,
-Vlad
next prev parent reply other threads:[~2003-03-03 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 10:56 2.4 and cryptofs on raid1 - what will be cached and how many times Vlad Harchev
2003-03-03 9:38 ` Vlad Harchev [this message]
2003-03-03 21:50 ` Neil Brown
2003-03-04 9:30 ` Vlad Harchev
2003-03-04 9:20 ` Jörn Engel
2003-03-04 11:31 ` Vlad Harchev
2003-03-04 11:07 ` Bryan Andersen
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=20030303093832.GA4601@h \
--to=hvv@hippo.ru \
--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