Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753898Ab0GEK5N (ORCPT ); Mon, 5 Jul 2010 06:57:13 -0400 Received: from a.mx.secunet.com ([195.81.216.161]:53437 "EHLO a.mx.secunet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751009Ab0GEK5I (ORCPT ); Mon, 5 Jul 2010 06:57:08 -0400 Date: Mon, 5 Jul 2010 12:58:55 +0200 From: Steffen Klassert To: Dan Kruchinin Cc: LKML , Herbert Xu Subject: Re: [PATCH 1/3] padata: separate serial and parallel cpumasks Message-ID: <20100705105855.GL10072@secunet.com> References: <20100702085323.GF10072@secunet.com> <20100702091726.GH10072@secunet.com> <20100702111138.GI10072@secunet.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-OriginalArrivalTime: 05 Jul 2010 10:57:03.0079 (UTC) FILETIME=[CCD63770:01CB1C30] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 766 Lines: 22 On Fri, Jul 02, 2010 at 05:01:28PM +0400, Dan Kruchinin wrote: > > Sounds good. But if I understand linux crypto framework right, it > calls init_tfm every time it creates new security association. Ideally > pcrypt should have only two cpumasks one for pencrypt instance and > another for pdecrypt. > If we'll initialize these cpumasks in pcrypt_alloc_tfm they'll be > initialized every time new SA appears. Yes, you are absolutely right. Placing this to instance context is the right way to do it. Thanks, Steffen -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/