From: Igor Novgorodov <igor@novg.net>
To: Milan Broz <mbroz@redhat.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] AES-XTS performance
Date: Tue, 16 Nov 2010 10:31:02 +0300 [thread overview]
Message-ID: <737699007.20101116103102@novg.net> (raw)
In-Reply-To: <4CE142C3.1070408@redhat.com>
> Loop is not ideal device to test but it is not the problem.
> The main problem is that dm-crypt uses only one core per device.
> If you want to do some tests, try this patch
> http://lkml.org/lkml/2010/11/12/344
> (but there is still some issues and it will not help much
> if only one process generates IOs.)
I've tried to apply this patch against 2.6.36 and 2.6.37-rc2
but without success:
# patch -p1 -i ./dm-crypt-patch.diff
patching file drivers/md/dm-crypt.c
Hunk #2 FAILED at 78.
Hunk #3 succeeded at 91 with fuzz 2.
Hunk #4 FAILED at 133.
Hunk #5 FAILED at 152.
Hunk #7 FAILED at 227.
Hunk #8 FAILED at 239.
Hunk #9 FAILED at 259.
Hunk #10 FAILED at 336.
Hunk #11 FAILED at 358.
Hunk #12 FAILED at 381.
Hunk #13 FAILED at 501.
Hunk #14 FAILED at 546.
Hunk #15 FAILED at 562.
Hunk #16 succeeded at 574 with fuzz 2.
Hunk #17 FAILED at 583.
Hunk #19 succeeded at 1065 with fuzz 1.
Hunk #20 FAILED at 1096.
Hunk #21 FAILED at 1136.
Hunk #22 FAILED at 1155.
Hunk #23 FAILED at 1174.
Hunk #24 FAILED at 1209.
Hunk #25 FAILED at 1240.
Hunk #26 FAILED at 1259.
Hunk #27 FAILED at 1323.
Hunk #28 FAILED at 1354.
Hunk #29 FAILED at 1365.
Hunk #30 FAILED at 1378.
Hunk #31 FAILED at 1405.
25 out of 31 hunks FAILED -- saving rejects to file drivers/md/dm-crypt.c.rej
What version of kernel should i patch? GIT?
next prev parent reply other threads:[~2010-11-16 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 12:36 [dm-crypt] AES-XTS performance Igor Novgorodov
2010-11-15 14:25 ` Milan Broz
2010-11-16 6:53 ` Igor Novgorodov
2010-11-16 7:31 ` Igor Novgorodov [this message]
2010-11-16 9:25 ` Milan Broz
2010-11-16 11:32 ` Igor Novgorodov
2010-11-16 12:00 ` Milan Broz
2010-11-17 10:03 ` Igor Novgorodov
2010-11-17 23:39 ` Jakob-Tobias Winter
2010-11-15 14:38 ` Arno Wagner
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=737699007.20101116103102@novg.net \
--to=igor@novg.net \
--cc=dm-crypt@saout.de \
--cc=mbroz@redhat.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.