From: Michael Halcrow <mhalcrow@us.ibm.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
ecryptfs-devel@lists.sourceforge.net, trevor.highland@gmail.com,
mhalcrow@us.ibm.com
Subject: [PATCH 0/3] eCryptfs: extent offset fix, crypto performance, and larger header regions
Date: Fri, 2 Nov 2007 13:50:33 -0500 [thread overview]
Message-ID: <20071102185033.GB30487@localhost.austin.ibm.com> (raw)
This patch set includes some minor fixes for eCryptfs, including:
- An enhancement to allow larger header regions
- A bugfix for hosts with page size >4K
- An enhancement to reduce crypto overhead
I recommend merging at least the bugfix into 2.6.24.
next reply other threads:[~2007-11-02 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 18:50 Michael Halcrow [this message]
2007-11-02 18:51 ` [PATCH 1/3] eCryptfs: Track header bytes rather than extents Michael Halcrow
2007-11-02 18:52 ` [PATCH 2/3] eCryptfs: Increment extent_offset once per loop interation Michael Halcrow
2007-11-02 18:53 ` [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation Michael Halcrow
2007-11-02 20:10 ` Andrew Morton
2007-11-02 20:18 ` 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=20071102185033.GB30487@localhost.austin.ibm.com \
--to=mhalcrow@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=ecryptfs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trevor.highland@gmail.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