All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: "Thomas Bächler" <thomas@archlinux.org>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt multithreaded yet?
Date: Wed, 08 Aug 2012 17:45:08 +0200	[thread overview]
Message-ID: <50228984.5090708@redhat.com> (raw)
In-Reply-To: <5022864F.8030402@archlinux.org>

On 08/08/2012 05:31 PM, Thomas Bächler wrote:
> This is in 2.6.38 and later, I think:

No, it is not. This is something different.

In current kernel is per-cpu changes but it will not use
parallel cpu cores if it is submitted from the same cpu.

Mikulas' patches tries to create parallel threads and run
operations on all cores (plus some other changes as sorting).

Milan

  reply	other threads:[~2012-08-08 15:45 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 [this message]
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
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=50228984.5090708@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=thomas@archlinux.org \
    /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.