From: David Miller <davem@davemloft.net>
To: harvey.harrison@gmail.com
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 18/23] sparc: use the new byteorder headers
Date: Tue, 19 Aug 2008 01:43:50 -0700 (PDT) [thread overview]
Message-ID: <20080819.014350.79505195.davem@davemloft.net> (raw)
In-Reply-To: <1219106897.17033.71.camel@brick>
From: Harvey Harrison <harvey.harrison@gmail.com>
Date: Mon, 18 Aug 2008 17:48:17 -0700
> Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
I'm not so sure about this.
If I understand the ___swab*() inlines in linux/swab.h,
it has the following priority of swapping methods:
1) If arch defines __arch_swab*(), this is used.
2) If arch defines __arch_swab*p(), variable is popped onto
the stack and we do the pointer based operation.
3) Else normal C version is used.
Case #2 is totally disagree with.
Especially for small swaps such as 16-bit the inline expansion
of the portable C code is going to be much better than popping
the variable onto and then back off the stack.
Sparc 64-bit only provides the __arch_swab*p() routines so
#2 is what will in fact be used here.
So NACK based upon that analysis.
next prev parent reply other threads:[~2008-08-19 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 0:48 Harvey Harrison
2008-08-19 8:43 ` David Miller [this message]
2008-08-19 19:02 ` Harvey Harrison
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=20080819.014350.79505195.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@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
all inboxes | Powered by JetHome®