From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756901Ab0IGOGu (ORCPT ); Tue, 7 Sep 2010 10:06:50 -0400 Received: from bombadil.infradead.org ([18.85.46.34]:52386 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756181Ab0IGOGr (ORCPT ); Tue, 7 Sep 2010 10:06:47 -0400 Date: Tue, 7 Sep 2010 10:06:46 -0400 From: Christoph Hellwig To: Herbert Xu Cc: Linux Crypto Mailing List , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: RFC: Crypto API User-interface Message-ID: <20100907140646.GA31921@infradead.org> References: <20100907084213.GA4610@gondor.apana.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100907084213.GA4610@gondor.apana.org.au> User-Agent: Mutt/1.5.20 (2009-08-17) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 07, 2010 at 04:42:13PM +0800, Herbert Xu wrote: > Hi: > > This is what I am proposing for the Crypto API user-interface. Can you explain why we would ever want a userspace interface to it? doing crypto in kernel for userspace consumers sis simply insane. It's computational intensive code which has no business in kernel space unless absolutely required (e.g. for kernel consumers). In addition to that adding the context switch overhead and address space transitions is god awfull too. This all very much sounds like someone had far too much crack.