From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: Request for review of Linux iSCSI driver version 4.0.0.1 Date: Wed, 26 Nov 2003 13:41:38 +0000 Sender: linux-scsi-owner@vger.kernel.org Message-ID: <20031126134138.A5897@infradead.org> References: <200310231734.10263.krmurthy@cisco.com> <20031027153932.A16679@infradead.org> <20031121173236.GX30485@parcelfarce.linux.theplanet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from phoenix.infradead.org ([213.86.99.234]:38406 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S263591AbTKZNll (ORCPT ); Wed, 26 Nov 2003 08:41:41 -0500 Content-Disposition: inline In-Reply-To: ; from chaapala@cisco.com on Fri, Nov 21, 2003 at 12:18:17PM -0600 List-Id: linux-scsi@vger.kernel.org To: Clay Haapala Cc: Matthew Wilcox , Christoph Hellwig , Krishna Murthy , linux-scsi@vger.kernel.org, davmyers@cisco.com On Fri, Nov 21, 2003 at 12:18:17PM -0600, Clay Haapala wrote: > Question: Should the implementation use the crypto api > or be added to the lib/crc32 code? I've talen a quick look at the code and it looks like you're doing the crc not only for control but also for data packages, thus it seems the best idea to make it a digest in the crypto framework.