From: Adrian Bunk <bunk@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] asm-generic/int-ll64.h: always provide __{s,u}64
Date: Tue, 20 May 2008 03:13:45 +0300 [thread overview]
Message-ID: <20080520001345.GG17716@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <48321299.80303@zytor.com>
On Mon, May 19, 2008 at 04:51:53PM -0700, H. Peter Anvin wrote:
> Adrian Bunk wrote:
>>>>
>>> If it is going to be unconditionally offered, we could get rid of
>>> __BYTEORDER_HAS_U64__ as a next step. Unless there is something I've
>>> missed.
>>
>> Why do we need the byteorder headers in userspace at all?
>>
>
> Because Linux-specific software has depended on them for over 15 years
> (they are a much better API than anything POSIX provides.) We can't
> just yank them, and so it's better if they actually work.
>
> Yes, you can argue it should be glibc's job to provide them, but well,
> why duplicate work when we already have a nicely working set.
The worst thing is how many CONFIG_'s they currently leak to userspace.
And e.g. the versions in the x86 header are therefore not the fastest
ones (unless the userspace software #define's CONFIG_X86_BSWAP)...
> -hpa
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-05-20 0:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 21:54 Adrian Bunk
2008-05-19 22:01 ` H. Peter Anvin
2008-05-19 22:27 ` Harvey Harrison
2008-05-19 22:29 ` H. Peter Anvin
2008-05-19 22:32 ` Adrian Bunk
2008-05-19 23:51 ` H. Peter Anvin
2008-05-20 0:13 ` Adrian Bunk [this message]
2008-05-20 0:17 ` H. Peter Anvin
2008-05-20 0:33 ` Adrian Bunk
2008-05-20 1:16 ` H. Peter Anvin
2008-05-20 9:09 ` Adrian Bunk
2008-05-20 14:54 ` H. Peter Anvin
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=20080520001345.GG17716@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.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®