From: Tyler Hicks <tyhicks@canonical.com>
To: "Georg Schönberger" <gschoenberger@thomas-krenn.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: ecryptfs o_direct
Date: Mon, 11 Jun 2012 08:04:06 -0700 [thread overview]
Message-ID: <20120611150405.GA4748@boyd> (raw)
In-Reply-To: <4FD59617.1010608@thomas-krenn.com>
[-- Attachment #1: Type: text/plain, Size: 616 bytes --]
On 2012-06-11 08:54:15, Georg Schönberger wrote:
> Hello everyone,
>
> is there a short explanation available why ecryptfs is not working with
> direct I/O?
No one has written the code required for eCryptfs to support direct I/O.
Tyler
> According to Jens Axboe I cannot use FIO with option "direct=1" because
> my encrypted home partition with ecryptfs is not supporting O_DIRECT.
>
> -Georg
> --
> To unsubscribe from this list: send the line "unsubscribe ecryptfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-06-11 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 6:54 ecryptfs o_direct Georg Schönberger
2012-06-11 15:04 ` Tyler Hicks [this message]
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=20120611150405.GA4748@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=gschoenberger@thomas-krenn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox