From: Milan Broz <gmazyland@gmail.com>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt multithreaded yet?
Date: Sun, 16 Dec 2012 19:15:10 +0100 [thread overview]
Message-ID: <50CE0FAE.6030707@gmail.com> (raw)
In-Reply-To: <50CDBA37.1050308@interlinx.bc.ca>
On 12/16/2012 01:10 PM, Brian J. Murrell wrote:
> On 12-08-08 11:39 AM, Milan Broz wrote:
>>
>> Anyway, I have patches rebased for 3.5/3.6-rc here
>> http://mbroz.fedorapeople.org/dm-crypt/
>
> Unfortunately the files in http://mbroz.fedorapeople.org/dm-crypt/3.6-rc
> all return 403 trying to fetch them.
No idea why it turned world non-readable, fixed.
>> If you can test it and prove it helps for your use case, its would
>> be nice. Just take it as experimental, there can be bugs still.
>
> I was going to try this on an FC18 kernel. Are you using these patches
> by any chance?
But I am afraid I did not find any real situation where these patches
really helps (AND not cause problems with different pattern).
See also discussion on dm-devel list, I still think generic
kernel workqueues should be used to provide such parallelization and
we should not duplicate code in dm-crypt...
My suggestion is that using AES-NI extension helps much more with
the current upstream code than anything else (for AES, obviously).
Milan
next prev parent reply other threads:[~2012-12-16 18:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 14:29 [dm-crypt] dm-crypt multithreaded yet? Brian J. Murrell
2012-08-08 15:31 ` Thomas Bächler
2012-08-08 15:45 ` Milan Broz
2012-08-09 3:17 ` Marc MERLIN
2012-08-09 10:09 ` Brian J. Murrell
2012-08-08 15:39 ` Milan Broz
2012-12-16 12:10 ` Brian J. Murrell
2012-12-16 18:15 ` Milan Broz [this message]
2012-12-16 21:29 ` Heinz Diehl
2012-12-16 21:43 ` Brian J. Murrell
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=50CE0FAE.6030707@gmail.com \
--to=gmazyland@gmail.com \
--cc=brian@interlinx.bc.ca \
--cc=dm-crypt@saout.de \
/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.