From: Herbert Xu Subject: Re: Clarification of allowed context for crypto routines Date: Wed, 28 Jan 2009 14:08:02 +1100 Message-ID: <20090128030802.GA5536@gondor.apana.org.au> References: <20090124093245.GA4889@gondor.apana.org.au> <200901272101.20190.arvidjaar@mail.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org To: Andrey Borzenkov Return-path: Received: from rhun.apana.org.au ([64.62.148.172]:57178 "EHLO arnor.apana.org.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751691AbZA1DII (ORCPT ); Tue, 27 Jan 2009 22:08:08 -0500 Content-Disposition: inline In-Reply-To: <200901272101.20190.arvidjaar@mail.ru> Sender: linux-crypto-owner@vger.kernel.org List-ID: On Tue, Jan 27, 2009 at 09:01:13PM +0300, Andrey Borzenkov wrote: > > - all usage is kmap_atomic; which implies it should be technically safe > (not advisable) to use in interrupt context as well kmap_atomic has limited slots, we currently use two slots for process context and two slots for softirq context. Adding support for hardirq context can be done by using another two slots but that would mean adding another conditional branch in the code path. As it stands I have not seen any convincing use cases that would justify this. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt