From: Ed L Cashin <ecashin@coraid.com>
To: linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Jim MacBaine <jmacbaine@gmail.com>
Subject: Re: aoe fails on sparc64
Date: Thu, 01 Sep 2005 15:13:52 -0400 [thread overview]
Message-ID: <87k6i0bnyn.fsf@coraid.com> (raw)
In-Reply-To: 20050831.232430.50551657.davem@davemloft.net
"David S. Miller" <davem@davemloft.net> writes:
> From: Ed L Cashin <ecashin@coraid.com>
...
>> OK. 67553994410557440 is 61440 byte swapped in 64 bits, and 30MB is
>> 61440 sectors, so this should be a simple byte order fix.
>
> More strangely, the upper and lower 32-bit words are swapped.
> The bytes within each 32-bit word are swapped correctly.
>
> So the calculation maybe should be something like:
>
> __le32 *p = (__le32 *) &id[100 << 1];
> u32 high32 = le32_to_cpup(p);
> u32 low32 = le32_to_cpup(p + 1);
>
> ssize = (((u64)high32 << 32) | (u64) low32);
>
> But that doesn't make any sense, and even ide_fix_driveid() in
> drivers/ide/ide-iops.c does a le64_to_cpu() for this value:
>
> id->lba_capacity_2 = __le64_to_cpu(id->lba_capacity_2);
>
> I wonder if this is some artifact of how AOE devices encode
> this field when sending it to the client.
Well, an EtherDrive blade just copies the ATA identify response data
into a network packet without looking at it. The vblade, though, has
to set the lba_capacity and lba_capacity_2 fields itself.
The aoe driver looks OK, but it turns out there's a byte swapping bug
in the vblade that could be related if he's running the vblade on a
big endian host (even though he said it was an x86 host), but I
haven't heard back from the original poster yet.
The vblade bug was the omission of swapping the bytes in each short.
The fix below shows what I mean:
diff -urNp a-exp/ata.c b-exp/ata.c
--- a-exp/ata.c 2005-09-01 10:19:11.000000000 -0400
+++ b-exp/ata.c 2005-09-01 10:19:12.000000000 -0400
@@ -55,24 +55,29 @@ setfld(ushort *a, int idx, int len, char
}
static void
-setlba28(ushort *p, vlong lba)
+setlba28(ushort *ident, vlong lba)
{
- p += 60;
- *p++ = lba & 0xffff;
- *p = lba >> 16 & 0x0fffffff;
+ uchar *cp;
+
+ cp = (uchar *) &ident[60];
+ *cp++ = lba;
+ *cp++ = lba >>= 8;
+ *cp++ = lba >>= 8;
+ *cp++ = (lba >>= 8) & 0xf;
}
static void
-setlba48(ushort *p, vlong lba)
+setlba48(ushort *ident, vlong lba)
{
- p += 100;
- *p++ = lba;
- lba >>= 16;
- *p++ = lba;
- lba >>= 16;
- *p++ = lba;
- lba >>= 16;
- *p = lba;
+ uchar *cp;
+
+ cp = (uchar *) &ident[100];
+ *cp++ = lba;
+ *cp++ = lba >>= 8;
+ *cp++ = lba >>= 8;
+ *cp++ = lba >>= 8;
+ *cp++ = lba >>= 8;
+ *cp++ = lba >>= 8;
}
void
--
Ed L Cashin <ecashin@coraid.com>
next prev parent reply other threads:[~2005-09-01 19:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-31 13:30 aoe fails on sparc64 Jim MacBaine
2005-08-31 15:50 ` Ed L Cashin
2005-09-01 6:24 ` David S. Miller
2005-09-01 19:13 ` Ed L Cashin [this message]
2005-09-01 19:45 ` David S. Miller
2005-09-03 16:06 ` Jim MacBaine
2005-09-06 20:31 ` Ed L Cashin
2005-09-09 14:06 ` Ed L Cashin
2005-09-16 13:36 ` Ed L Cashin
2005-09-16 20:34 ` David S. Miller
2005-09-16 23:35 ` David S. Miller
2005-09-17 10:10 ` Jim MacBaine
2005-09-18 6:12 ` David S. Miller
2005-09-19 14:24 ` Ed L Cashin
2005-09-19 18:21 ` David S. Miller
2005-09-19 18:29 ` Roland Dreier
2005-09-19 18:38 ` Ed L Cashin
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=87k6i0bnyn.fsf@coraid.com \
--to=ecashin@coraid.com \
--cc=davem@davemloft.net \
--cc=jmacbaine@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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