Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation

On Fri, 2 Nov 2007 13:53:08 -0500
Michael Halcrow <[email protected]> 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 <[email protected]>
> Signed-off-by: Michael Halcrow <[email protected]>

I've inferred from this that Michael authored this patch.  Please
let me know if that was incorrect.

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation
    • From: Michael Halcrow <[email protected]>

• References:
  • [PATCH 0/3] eCryptfs: extent offset fix, crypto performance, and larger header regions
    • From: Michael Halcrow <[email protected]>
  • [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation
    • From: Michael Halcrow <[email protected]>

• Prev by Date: Re: [PATCH/RFC] eradicate bashisms in scripts/patch-kernel
• Next by Date: [PATCH] mtrr use type bool [RESEND]
• Previous by thread: [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation
• Next by thread: Re: [PATCH 3/3] eCryptfs: Set inode key only once per crypto operation
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]