From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267934AbUHFCrj (ORCPT ); Thu, 5 Aug 2004 22:47:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268063AbUHFCrj (ORCPT ); Thu, 5 Aug 2004 22:47:39 -0400 Received: from mx1.redhat.com ([66.187.233.31]:22721 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S267934AbUHFCr3 (ORCPT ); Thu, 5 Aug 2004 22:47:29 -0400 Date: Thu, 5 Aug 2004 22:47:12 -0400 (EDT) From: James Morris X-X-Sender: jmorris@dhcp83-76.boston.redhat.com To: Jean-Luc Cooke cc: Michal Ludvig , , , "David S. Miller" Subject: Re: [PATCH] In-Reply-To: <20040805194914.GC23994@certainkey.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 5 Aug 2004, Jean-Luc Cooke wrote: > Would you be against a patch to cryptoapi to have access to a > non-scatter-list set of calls? > > I know a few people would like to see that , and I would also like to use > some low-level: > > crypto_digest_update_byte(struct digest_alg *digest, > unsigned char *buf, > unsigned int nbytes); > crypto_cipher_encrypt_byte(struct cipher_alg *cipher, > unsigned char *dst, > unsigned char *src, > unsigned int nbytes); > > I'm in the middle of preparing for a paper and would like to get code running > without scatterlists. The idea of the scatterlist API is to encourage encryption at the page level. Can you demonstrate a compelling need for raw access to the algorithms via the API? - James -- James Morris