public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Clay Haapala <chaapala@cisco.com>
To: James Morris <jmorris@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	"David S. Miller" <davem@redhat.com>,
	mpm@selenic.com
Subject: Re: [PATCH 2.6.1] Add CRC32C chksums to crypto and lib routines
Date: Wed, 04 Feb 2004 11:07:45 -0600	[thread overview]
Message-ID: <yqujisimepsu.fsf@chaapala-lnx2.cisco.com> (raw)
In-Reply-To: <Xine.LNX.4.44.0402031207330.939-100000@thoron.boston.redhat.com> (James Morris's message of "Tue, 3 Feb 2004 12:09:56 -0500 (EST)")

On Tue, 3 Feb 2004, James Morris told this:
> On Tue, 3 Feb 2004, Clay Haapala wrote:
> 
>> If this patch looks good, I'd like it accepted so we can submit
>> code iSCSI driver code that makes use of it.  This may be a good
>> time, since the crypto SHA code is getting a little scrutiny right
>> now.
> 
> This will need to wait until 2.6.2 is released, and will you also
> please submit the iSCSI change for review?
> 
Thanks, Dave, for setting me straight on not posting mondo patches to
lkml. :-)

The 4.0.0.4 version of the driver, with the crypto CRC calls omitted,
has been submitted for review by the scsi maintainers.  Here is link
to a "preview" patch with the calls to the crypto CRC32C module back
in, but without any of their latest comments incorporated:

  http://home.mn.rr.com/haapi/iSCSI/iscsi-4.0.0.4-with-crypto.patch.bz2

iscsi-crc.{c,h} are just wrappers for code using the previous private
implementation.  iscsi-recv-pdu.c and iscsi-xmit-pdu.c have the code
which processes scatterlists and make calls to the crypto CRC32C
routines in the other patch.

This code has been tested successfully on 2.6.1 with udev-0.15 and late-model
sysfs, hotplug, and klibc.  The patch also contains the iscsi utilities
code, if you want to go the whole nine yards.
-- 
Clay Haapala (chaapala@cisco.com) Cisco Systems SRBU +1 763-398-1056
   6450 Wedgwood Rd, Suite 130 Maple Grove MN 55311 PGP: C89240AD
    Minnesota is a very agreeable state.  Lately even Celsius and
                   Fahrenheit have tended to agree.

  reply	other threads:[~2004-02-04 17:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-14 21:31 [PATCH] Add CRC32C chksums to crypto routines Clay Haapala
2004-01-14 21:45 ` James Morris
2004-01-14 22:12   ` Clay Haapala
2004-01-16  1:40 ` Matt Mackall
2004-01-19 20:13 ` James Morris
2004-01-19 21:15   ` Clay Haapala
2004-01-19 21:33     ` James Morris
2004-02-03 16:58       ` [PATCH 2.6.1] Add CRC32C chksums to crypto and lib routines Clay Haapala
2004-02-03 17:09         ` James Morris
2004-02-04 17:07           ` Clay Haapala [this message]
2004-02-03 17:13         ` James Morris
2004-02-03 17:50           ` [PATCH 2.6.1 -- take two] " Clay Haapala
2004-02-03 18:51             ` Matt Mackall
2004-02-03 19:13               ` Clay Haapala
2004-02-03 19:27                 ` Matt Mackall
2004-02-03 20:17                   ` James Morris
2004-02-03 23:25                 ` Matt Domsch
2004-02-03 23:37                   ` Matt Mackall
2004-02-04 16:14                     ` Clay Haapala
2004-02-06 23:54                       ` Jamie Lokier
2004-02-04  2:18                   ` James Morris
2004-02-04  3:11                   ` Valdis.Kletnieks

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yqujisimepsu.fsf@chaapala-lnx2.cisco.com \
    --to=chaapala@cisco.com \
    --cc=davem@redhat.com \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mpm@selenic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox