From: Tomasz Chmielewski <mangoo@wpkg.org>
To: device-mapper development <dm-devel@redhat.com>
Cc: dm-crypt@saout.de
Subject: Re: SMP-aware kcryptd?
Date: Mon, 13 Apr 2009 19:47:16 +0200 [thread overview]
Message-ID: <49E37AA4.8060007@wpkg.org> (raw)
In-Reply-To: <49E37824.8010100@redhat.com>
Milan Broz schrieb:
> Tomasz Chmielewski wrote:
>> Currently, the trend with CPUs is to add more cores rather than increase
>> the speed of a single core.
>>
>> This does not scale very well with certain things in the Linux kernel.
>> One of them is kcryptd.
>>
>>
>> A system able to deliver data with a speed of ~200 MB/s from a RAID
>> array, will be only able to deliver a fraction of it (i.e. ~40 MB/s in
>> my case) when reads are being done from a dm-crypt device.
(...)
> Anyway, it is not highest priority currently... but still in slow progress.
> (but I guess high speed SSDs will increase priority for this too,
> currently it is real problem only for RAID arrays:-)
And, laptops/netbooks with (slow) multi-core CPUs.
Encryption is getting popular there as well.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2009-04-13 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 13:41 SMP-aware kcryptd? Tomasz Chmielewski
2009-04-13 17:36 ` Milan Broz
2009-04-13 17:47 ` Tomasz Chmielewski [this message]
2009-04-13 19:33 ` Larry Dickson
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=49E37AA4.8060007@wpkg.org \
--to=mangoo@wpkg.org \
--cc=dm-crypt@saout.de \
--cc=dm-devel@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.