From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268127AbUHFNHZ (ORCPT ); Fri, 6 Aug 2004 09:07:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268128AbUHFNHY (ORCPT ); Fri, 6 Aug 2004 09:07:24 -0400 Received: from 104.engsoc.carleton.ca ([134.117.69.104]:63933 "EHLO certainkey.com") by vger.kernel.org with ESMTP id S268127AbUHFNHX (ORCPT ); Fri, 6 Aug 2004 09:07:23 -0400 Date: Fri, 6 Aug 2004 09:03:03 -0400 From: Jean-Luc Cooke To: Linus Torvalds Cc: Michael Halcrow , James Morris , "David S. Miller" , cryptoapi@lists.logix.cz, Michal Ludvig , linux-kernel@vger.kernel.org Subject: Re: [PATCH] Message-ID: <20040806130303.GF23994@certainkey.com> References: <20040805194914.GC23994@certainkey.com> <20040806020313.GA21309@halcrow.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040523i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 05, 2004 at 09:58:58PM -0700, Linus Torvalds wrote: > So I'd strongly suggest against doing any "raw crypto access". Zero-copy > is often just a complicated way of doing things slowly, all in the name of > some benchmark performance. I hear you, these are all desirable things and I hate trying to be the black sheep - but would random.c make sense in being the exception since the outward looking interfaces (random_write for example) all use const char* type as arguments? Keeping the existing random.c interface and using crypto-api's scatter-gather interface are kind of contradictory ... or and I really missing something important (likely)? JLC