From: Manfred Spraul <manfred@colorfullife.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-arch@vger.kernel.org
Subject: Re: posix message queues
Date: Wed, 07 Apr 2004 21:15:44 +0200 [thread overview]
Message-ID: <40745360.6000709@colorfullife.com> (raw)
In-Reply-To: <20040407120720.6b937deb.akpm@osdl.org>
Andrew Morton wrote:
>Manfred, if/when this gets merged up the long-suffering arch maintainers
>might appreciate a little test app to exercise the syscalls which must be
>added. Do you have something suitable at hand?
>
>
I have a few separate apps, I'll merge them into one app and post it to
lkml. Probably tomorrow or Friday.
>
>Also, before we go too far the 64-bit guys may like to comment on the
>syscall interface. For example, this:
>
>struct mq_attr {
> long mq_flags; /* message queue flags */
> long mq_maxmsg; /* maximum number of messages */
> long mq_msgsize; /* maximum message size */
> long mq_curmsgs; /* number of messages currently queued */
> long __reserved[4]; /* ignored for input, zeroed for output */
>};
>
>looks like it will require emulation for 32-bit apps. But if we were to
>make these __u32 perhaps that could be avoided?
>
>
No. The unix spec mandates 'long' for the final C-library api. Using u32
would mean that glibc would have to add an emulation layer in user space
for 64-bit archs. In the long run, 64-bit kernels running 64-bit apps
will be the common case. I don't want to add an emulation layer to the
common case.
--
Manfred
next prev parent reply other threads:[~2004-04-07 19:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 19:07 posix message queues Andrew Morton
2004-04-07 19:15 ` Manfred Spraul [this message]
2004-04-08 8:17 ` Arnd Bergmann
2004-04-08 8:49 ` Andrew Morton
2004-04-08 14:08 ` Manfred Spraul
2004-04-08 20:24 ` Andrew Morton
2004-04-09 23:45 ` David S. Miller
2004-04-10 11:19 ` Manfred Spraul
2004-04-10 11:53 ` Manfred Spraul
2004-04-10 20:43 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2004-04-08 22:22 Arnd Bergmann
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=40745360.6000709@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@osdl.org \
--cc=linux-arch@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