From: Milan Broz <mbroz@redhat.com>
To: Igor Novgorodov <igor@novg.net>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] AES-XTS performance
Date: Tue, 16 Nov 2010 13:00:08 +0100 [thread overview]
Message-ID: <4CE27248.5010205@redhat.com> (raw)
In-Reply-To: <1373448030.20101116143225@novg.net>
On 11/16/2010 12:32 PM, Igor Novgorodov wrote:
> Such big difference between read and write speed is by design?
> Or it is a problem of my setup? Maybe i should try to disable
> hyperthreading and check again?
That should be probably improved later.
(btw I just fixed stacking there, it was written by Andi Kleen).
Anyway, now I need to check that there is no known data corruption
with this approach and then we can add another patches on top of it.
(Targeted for 2.6.38, it missed 2.6.37 merge window already.)
(If anyone see some reproducible data corruption when using this patch,
please let me know.)
Milan
next prev parent reply other threads:[~2010-11-16 12:00 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
2010-11-16 9:25 ` Milan Broz
2010-11-16 11:32 ` Igor Novgorodov
2010-11-16 12:00 ` Milan Broz [this message]
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=4CE27248.5010205@redhat.com \
--to=mbroz@redhat.com \
--cc=dm-crypt@saout.de \
--cc=igor@novg.net \
/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