From: Harvey Harrison <harvey.harrison@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] byteorder: eliminate pointer bytorder api
Date: Tue, 20 May 2008 15:15:25 -0700 [thread overview]
Message-ID: <1211321725.5915.208.camel@brick> (raw)
In-Reply-To: <20080520.141731.99514303.davem@davemloft.net>
On Tue, 2008-05-20 at 14:17 -0700, David Miller wrote:
> From: Harvey Harrison <harvey.harrison@gmail.com>
> Date: Tue, 20 May 2008 12:24:09 -0700
>
> > Not a great api, should be using cpu_to_etc and deref the pointer yourself.
> > cpu_to_le16p
> > cpu_to_le32p
> > cpu_to_le64p
> > cpu_to_be16p
> > cpu_to_be32p
> > cpu_to_be64p
> >
> > Replaced by the aligned get_/put_ helpers
> > le16_to_cpup
> > le32_to_cpup
> > le64_to_cpup
> > be16_to_cpup
> > be32_to_cpup
> > be64_to_cpup
> >
> > Also add const to the get/put helpers and use them in the access_ok case for
> > unaligned access.
> >
> > Signed-off-by: Harvey Harrison <harvey.harrison@gmail.com>
>
> But what you're doing in the first patch is killing performance for some
> cases.
>
> The reason we use the cpu_to_*p() interfaces is to get the other-endian
> load and store instructions some processors have.
>
> What you're doing is undoing all of that work we've done to take
> advantage of such things.
Obviously I missed that part, my apologies. Would it be acceptable if,
taking the possibly arch-specific parts, moved the [endian]_to_cpup
name over to get_[endian]
ie:
le16_to_cpup -> get_le16
I'd leave cpu_to_le16p alone (it's not used that much anyway).
To make it similar to the get_unaligned_le16 helpers?
Thanks for having a look,
Harvey
next prev parent reply other threads:[~2008-05-20 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 19:24 [PATCH 2/2] byteorder: eliminate pointer bytorder api Harvey Harrison
2008-05-20 21:17 ` David Miller
2008-05-20 22:15 ` Harvey Harrison [this message]
2008-05-20 22:19 ` David Miller
2008-05-20 22:30 ` Harvey Harrison
2008-05-26 12:17 ` Jan Engelhardt
2008-05-27 22:40 ` 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=1211321725.5915.208.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--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