All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Halcrow <lkml@halcrow.us>
To: Pavel Machek <pavel@ucw.cz>
Cc: Phillip Hellewell <phillip@hellewell.homeip.net>,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	viro@ftp.linux.org.uk, mhalcrow@us.ibm.com, mcthomps@us.ibm.com,
	toml@us.ibm.com, yoder1@us.ibm.com,
	James Morris <jmorris@namei.org>,
	"Stephen C. Tweedie" <sct@redhat.com>,
	Erez Zadok <ezk@cs.sunysb.edu>,
	David Howells <dhowells@redhat.com>
Subject: Re: [PATCH 0/12: eCryptfs] eCryptfs version 0.1.6
Date: Thu, 4 May 2006 07:08:33 -0500	[thread overview]
Message-ID: <20060504120833.GA9194@halcrow.us> (raw)
In-Reply-To: <20060504072849.GC5359@ucw.cz>

On Thu, May 04, 2006 at 07:28:49AM +0000, Pavel Machek wrote:
> > processing the 4096-byte extents. The second modification is that
> > the header region occupies either 8192 bytes or the page size of
> > the host on which the file is created, whichever is larger. This
> > maximizes the probability that pages will be aligned between the
> > unencrypted and encrypted data, which is not a requirement, but it
> > helps with performance.
> 
> Does that mean that 10-bytes file now occupies 12KB disk space in
> common case of 4K filesystem?

Yes.

Mike

  reply	other threads:[~2006-05-04 12:13 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-04  3:17 [PATCH 0/12: eCryptfs] eCryptfs version 0.1.6 Phillip Hellewell
2006-05-04  3:27 ` [PATCH 1/13: eCryptfs] fs/Makefile and fs/Kconfig Phillip Hellewell
2006-05-04  3:35 ` [PATCH 2/13: eCryptfs] Documentation Phillip Hellewell
2006-05-04  7:32   ` Pavel Machek
2006-05-04 12:11     ` Michael Halcrow
2006-05-04  3:36 ` [PATCH 3/13: eCryptfs] Makefile Phillip Hellewell
2006-05-04  3:37 ` [PATCH 4/13: eCryptfs] Main module functions Phillip Hellewell
2006-05-04  3:37 ` [PATCH 5/13: eCryptfs] Header declarations Phillip Hellewell
2006-05-04 14:51   ` Pekka Enberg
2006-05-04 14:58     ` Artem B. Bityutskiy
2006-05-04 15:22       ` Pekka Enberg
2006-05-04 15:29         ` Artem B. Bityutskiy
2006-05-04 15:08     ` Michael Thompson
2006-05-04  3:38 ` [PATCH 6/13: eCryptfs] Superblock operations Phillip Hellewell
2006-05-04  9:55   ` Pavel Machek
2006-05-04 14:02     ` Michael Thompson
2006-05-04 14:26       ` Pekka Enberg
2006-05-04 14:37   ` Pekka Enberg
2006-05-04 15:00     ` Michael Thompson
2006-05-04 15:12       ` Pekka Enberg
2006-05-04 21:40     ` David Howells
2006-05-05 13:12       ` Dave Kleikamp
2006-05-05 14:03         ` David Howells
2006-05-05 14:34           ` Dave Kleikamp
2006-05-05 14:52             ` David Howells
2006-05-05 16:15   ` Timothy R. Chavez
2006-05-04  3:39 ` [PATCH 7/13: eCryptfs] Dentry operations Phillip Hellewell
2006-05-05 16:46   ` Timothy R. Chavez
2006-05-04  3:39 ` [PATCH 8/13: eCryptfs] File operations Phillip Hellewell
2006-05-04  4:06   ` Eric Dumazet
2006-05-05 18:55   ` Timothy R. Chavez
2006-05-04  3:40 ` [PATCH 9/13: eCryptfs] Inode operations Phillip Hellewell
2006-05-04  3:41 ` [PATCH 10/13: eCryptfs] Mmap operations Phillip Hellewell
2006-05-04 15:13   ` Pekka Enberg
2006-05-04 21:43     ` David Howells
2006-05-05 15:22       ` Dave Kleikamp
2006-05-05 15:38         ` Pekka Enberg
2006-05-06  2:21           ` Andrew Morton
2006-05-06 16:00             ` Michael Halcrow
2006-05-06 16:42               ` Andrew Morton
2006-05-06 16:57                 ` Linus Torvalds
2006-05-04  3:42 ` [PATCH 11/13: eCryptfs] Keystore Phillip Hellewell
2006-05-04  3:42 ` [PATCH 12/13: eCryptfs] Crypto functions Phillip Hellewell
2006-05-04  3:43 ` [PATCH 13/13: eCryptfs] Debug functions Phillip Hellewell
2006-05-04 20:30   ` Randy.Dunlap
2006-05-04  7:28 ` [PATCH 0/12: eCryptfs] eCryptfs version 0.1.6 Pavel Machek
2006-05-04 12:08   ` Michael Halcrow [this message]
2006-05-05  9:05 ` Alon Bar-Lev
2006-05-05 16:08   ` Michael Halcrow

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=20060504120833.GA9194@halcrow.us \
    --to=lkml@halcrow.us \
    --cc=akpm@osdl.org \
    --cc=dhowells@redhat.com \
    --cc=ezk@cs.sunysb.edu \
    --cc=jmorris@namei.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcthomps@us.ibm.com \
    --cc=mhalcrow@us.ibm.com \
    --cc=pavel@ucw.cz \
    --cc=phillip@hellewell.homeip.net \
    --cc=sct@redhat.com \
    --cc=toml@us.ibm.com \
    --cc=viro@ftp.linux.org.uk \
    --cc=yoder1@us.ibm.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.