public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
Cc: linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Mike Christie <michaelc@cs.wisc.edu>,
	James Bottomley <James.Bottomley@suse.de>,
	Konrad Rzeszutek Wilk <konrad@darnok.org>,
	Boaz Harrosh <bharrosh@panasas.com>,
	Richard Sharpe <realrichardsharpe@gmail.com>,
	Mike Christie <michaelc@cs.wisc.edu>,
	Vasu Dev <vasu.dev@linux.intel.com>,
	Joe Eykholt <jeykholt@cisco.com>
Subject: Re: [PATCH 0/2] lio-target: Add support for libcrypto crc32c and crc32-intel offload
Date: Mon, 13 Sep 2010 11:21:27 +0200	[thread overview]
Message-ID: <4C8DED17.6080801@suse.de> (raw)
In-Reply-To: <1284201076-22361-1-git-send-email-nab@linux-iscsi.org>

Nicholas A. Bellinger wrote:
> From: Nicholas Bellinger <nab@linux-iscsi.org>
> 
> Greetings all,
> 
> This patch series converts the LIO-Target fabric module from using a legacy
> internal slicing by 1x CRC32C algorithm to the slicing by 1x CRC32C available in
> crc32c.ko, as well as initial support for the Nehalem series crc32c-intel.ko
> instruction offload available since v2.6.27 in late 2008.
> 
> So far this series has been lightly tested with a handful of Open-iSCSI client VMs
> with the optimized crc32c-intel.ko offload case, and there appears to be some
> HeaderDigest failures for one case with RHEL6 B2 x86_64, while Ubuntu i686 on
> v2.6.27 and OpenSuse 11.2 x86_64 on v2.6.31 work as expected with HeaderDigest=CRC32C
> and DataDigest=CRC32C using the offload on the LIO-Target side.
> 
> Currently this patch disables the new iSCSI TPG attribute crc32c_x86_offload
> to force the crc32c.ko slicing by x1 CRC32C algorithm until these compatibility
> issues with existing libcrc32c clients can be properly resolved with the Nehalem
> CRC32C offload instructions running on the LIO-Target side.
> 
Due to a customer issue I had to revisit the CRC32 issue recently.
And according to you the main reason for using your own CRC routines
had been endianness issues.
IE the in-kernel crc32c routines apparently weren't able to
calculate the checksum in an endianness-independent manner.
So a CRC calculated on a BE machine would fail to be validated by a
LE machine and vice versa.

Has this been fixed / verified?

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2010-09-13  9:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-11 10:31 [PATCH 0/2] lio-target: Add support for libcrypto crc32c and crc32-intel offload Nicholas A. Bellinger
2010-09-13  9:21 ` Hannes Reinecke [this message]
2010-09-13 19:50   ` Nicholas A. Bellinger
2010-09-13 20:35     ` Mike Christie
2010-09-13 20:40       ` Nicholas A. Bellinger
2010-09-13 22:20         ` Nicholas A. Bellinger

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=4C8DED17.6080801@suse.de \
    --to=hare@suse.de \
    --cc=James.Bottomley@suse.de \
    --cc=bharrosh@panasas.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hch@lst.de \
    --cc=jeykholt@cisco.com \
    --cc=konrad@darnok.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=nab@linux-iscsi.org \
    --cc=realrichardsharpe@gmail.com \
    --cc=vasu.dev@linux.intel.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