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 yoZXY6cUq3P5 for ; Sun, 16 Dec 2012 22:25:12 +0100 (CET) Received: from mail-ee0-f50.google.com (mail-ee0-f50.google.com [74.125.83.50]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Sun, 16 Dec 2012 22:25:11 +0100 (CET) Received: by mail-ee0-f50.google.com with SMTP id b45so3070255eek.37 for ; Sun, 16 Dec 2012 13:25:11 -0800 (PST) Message-ID: <50CE3C33.2040900@gmail.com> Date: Sun, 16 Dec 2012 22:25:07 +0100 From: Milan Broz MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] multiple crypt devices not using multiple CPUs List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Brian J. Murrell" Cc: dm-crypt@saout.de On 12/16/2012 10:04 PM, Brian J. Murrell wrote: > Hi, > > I guess I must be missing something. I had understood that if one had > multiple block devices being crypted by dm-crypt, if they were being > operated on at the same time, their parallel crypto operations would > utilize different CPUs. In current kernels, work keeps on cpu which submitted it. Please read http://www.saout.de/pipermail/dm-crypt/2012-July/002582.html (and try to run the second case with direct-io, iow add oflag=direct for dd) m.