public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@coraid.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, jmacbaine@gmail.com
Subject: Re: aoe fails on sparc64
Date: Mon, 19 Sep 2005 14:38:26 -0400	[thread overview]
Message-ID: <877jdc2999.fsf@coraid.com> (raw)
In-Reply-To: <20050919.112159.55767801.davem@davemloft.net> (David S. Miller's message of "Mon, 19 Sep 2005 11:21:59 -0700 (PDT)")

"David S. Miller" <davem@davemloft.net> writes:

> From: Ed L Cashin <ecashin@coraid.com>
> Date: Mon, 19 Sep 2005 10:24:00 -0400
>
>>   1) Passing le64_to_cpup an unaligned pointer is "OK" and within the
>>      intended use of the function.  I'm having trouble finding whether
>>      this is documented somewhere.
>> 
>>   2) These new changes to the sparc64 unaligned access fault handling
>>      will make it OK to leave the aoe driver the way it is in the
>>      mainline kernel.
>
> Both #1 and #2 are true.

That's interesting.  I think I'll send a patch documenting #1.

> Although it's very much discouraged to dereference unaligned pointers,
> especially in performance critical code (which this AOE case is not,
> thankfully), because performance will be really bad as the trap
> handler has to fix up the access on RISC platforms.

Yes, this only happens when per AoE device when the AoE device is
discovered.  Still, I might submit a patch that reverts the aoe driver
to getting the ATA identify values byte by byte as it used to do.

-- 
  Ed L Cashin <ecashin@coraid.com>


      parent reply	other threads:[~2005-09-19 19:04 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
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 [this message]

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=877jdc2999.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