From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QtY0AP8dDUKI for ; Wed, 8 Aug 2012 17:39:28 +0200 (CEST) Received: from gerolde.archlinux.org (gerolde.archlinux.org [66.211.214.132]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 8 Aug 2012 17:39:28 +0200 (CEST) Received: from [134.61.95.56] (95-056.eduroam.rwth-aachen.de [134.61.95.56]) by gerolde.archlinux.org (Postfix) with ESMTPSA id 6953A9200E for ; Wed, 8 Aug 2012 11:30:39 -0400 (EDT) Message-ID: <5022864F.8030402@archlinux.org> Date: Wed, 08 Aug 2012 17:31:27 +0200 From: =?ISO-8859-15?Q?Thomas_B=E4chler?= MIME-Version: 1.0 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enigADA42BA0C6F284D2FAA92228" Subject: Re: [dm-crypt] dm-crypt multithreaded yet? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigADA42BA0C6F284D2FAA92228 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Am 08.08.2012 16:29, schrieb Brian J. Murrell: > I thought I knew the answer to this question (dm-crypt multithreaded > yet? no) but I had read in several places that dm-crypt had gained > multithreaded capabilities. I'm still skeptical though. I certainly > don't see it on Fedora 17's 3.3.4-5.fc17.x86_64 kernel. >=20 > Sadly, I don't have an AES-NI capable CPU, but I do have 4 (real, 8 wit= h > HT enabled) cores and dm-crypting on my SSD reduces its performance dow= n > from about 260MB/s (native) to 95MB/s. :-( I would like to think I > could get more performance out of it if more of the (usually available > anyway) CPU could be thrown at it. This is in 2.6.38 and later, I think: https://git.kernel.org/?p=3Dlinux/kernel/git/torvalds/linux.git;a=3Dcommi= tdiff;h=3Dc029772125594e31eb1a5ad9e0913724ed9891f2 The commit message also explains why you don't notice it. --------------enigADA42BA0C6F284D2FAA92228 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJQIoZSAAoJEChPw0yOSxoliEQP/jaPLVuhG4PxnBHhhuvGsYtC /cUeYwyE3BNdKkAvm0Prj4Qh+bUR9tg81iNuYQZ9+hMxMOoCjtGqVjWqu4qUAbwf H3SQ/q92/x0ji/EL7MXSRwY0yrOpdjEFn6PB3XBFhIaiDsE0vD9FL+wTUaKa1j/G dvknP+AgBRo57DwZ84lUus0HJyjT5pYy9B5g2l6Oyuj4MZlB88Six66Y4rSwFP1m QC7Hj3yNrOUE4tLaGfDvrOfXZtjeAVBwoWK2NMt/qdT+gZFvnf/wW5SjJGEx9pZr E9sqIa4ouu0xBL2UHA3m3htEJ1x1emgOqqxqMQNvSnRRZTzJYaU1CGTHslnKEZ/J fX3su+gJt6VvdJL2PBFL1D3JSY5STe7w08WbvObyFlYxUcw3XQ4opQxxxPLttzKB CHu8Gk3vQWb/o8OtUK0jPLURt9R05v8xx5J9tXwzuRPjUFv8itnwLy1FfFVFHOr2 oVJSKbinWkaRJDh/iZHFxKFgwoyAtELHbieZhJAnC6yeFRsupSw7U64IAlVrVc63 40+FxQn/QZqgGINh+q/+nQLXasE5mmVhrq+qOXtNChG63hXWVsv1jmx1OJLXxGWR aTbJSw2iGtBdb8vbT9Pqa7gB50a8FYq8DAZdv45shcVaDJfkH+LWyGNxbaP6pOFl Pn44AbuopCpiHcDam2gn =I/iF -----END PGP SIGNATURE----- --------------enigADA42BA0C6F284D2FAA92228--