From: Jes Sorensen <jes@wildopensource.com>
To: Andrew Vasquez <praka@users.sourceforge.net>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>, jeremy@sgi.com
Subject: Re: qla1280 endiannes and 64/32bit fixes
Date: 19 Jan 2004 03:54:02 -0500 [thread overview]
Message-ID: <yq08yk48gk5.fsf@wildopensource.com> (raw)
In-Reply-To: <20040118062157.GA11083@praka.local.home>
>>>>> "Andrew" == Andrew Vasquez <praka@users.sourceforge.net> writes:
Andrew> Either could I (but then again its late :). What I did notice
Andrew> was some rather weird code being executed when the CDB calls
Andrew> for no data to transfer (both 64/32_start). The code in
Andrew> question is this small snippet:
[snip]
Andrew> What exactly are we trying to zero out here? The IOCB has
Andrew> already been cleared with the following line earlier in the
Andrew> function:
Andrew,
I actually have zero clue why that code was looking like that, it goes
back to the original driver from before I started maintaining
it. Someone in a cube next to you must have written it.
Andrew> Jeremy: have you had any problems with running I/O down the
Andrew> 64bit capable IOCB path?
The 64bit IOCB path has been working great for quite a while, both on
Altix but also as far back as the BigSur boat anchors ;-)
I'll include your change with James' changes into the next release
(modulo the 64 bit addressing bit one as per your explanation).
Cheers,
Jes
next prev parent reply other threads:[~2004-01-19 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 23:40 qla1280 endiannes and 64/32bit fixes James Bottomley
2004-01-18 2:43 ` Jeremy Higdon
2004-01-18 3:16 ` James Bottomley
2004-01-18 6:21 ` Andrew Vasquez
2004-01-18 7:33 ` Jeremy Higdon
2004-01-18 14:54 ` James Bottomley
2004-01-18 21:59 ` Jes Sorensen
2004-01-19 17:40 ` Christoph Hellwig
2004-01-19 21:13 ` Jes Sorensen
2004-01-18 14:35 ` James Bottomley
2004-01-19 8:54 ` Jes Sorensen [this message]
2004-01-18 7:08 ` Jeremy Higdon
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=yq08yk48gk5.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=jeremy@sgi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=praka@users.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.