From: Michael Halcrow <mhalcrow@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
ecryptfs-devel@lists.sourceforge.net, trevor.highland@gmail.com
Subject: Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation
Date: Fri, 2 Nov 2007 15:18:35 -0500 [thread overview]
Message-ID: <20071102201835.GC30487@localhost.austin.ibm.com> (raw)
In-Reply-To: <20071102131031.3369e6e6.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
On Fri, Nov 02, 2007 at 01:10:31PM -0700, Andrew Morton wrote:
> On Fri, 2 Nov 2007 13:53:08 -0500
> Michael Halcrow <mhalcrow@us.ibm.com> wrote:
>
> > There is no need to keep re-setting the same key for any given
> > eCryptfs inode. This patch optimizes the use of the crypto API and
> > helps performance a bit.
> >
> > Signed-off-by: Trevor Highland <trevor.highland@gmail.com>
> > Signed-off-by: Michael Halcrow <mhalcrow@us.ibm.com>
>
> I've inferred from this that Michael authored this patch. Please
> let me know if that was incorrect.
Trevor Highland actually authored this one.
> The way in which we indicate authorship is to put a From: line right
> at the top of the changelog. If no such line appears then the From:
> line from the mail headers is used.
Noted.
Mike
[-- Attachment #2: Type: application/pgp-signature, Size: 481 bytes --]
prev parent reply other threads:[~2007-11-02 20:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 18:50 [PATCH 0/3] eCryptfs: extent offset fix, crypto performance, and larger header regions Michael Halcrow
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 [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=20071102201835.GC30487@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 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.