public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Benedyczak <golbi@mat.uni.torun.pl>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] 2/6 POSIX message queues
Date: Fri, 20 Feb 2004 19:11:46 +0100 (CET)	[thread overview]
Message-ID: <Pine.GSO.4.58.0402201848380.10845@Juliusz> (raw)
In-Reply-To: <200402201455.25782.arnd@arndb.de>

On Fri, 20 Feb 2004, Arnd Bergmann wrote:

> Krzysztof Benedyczak wrote:
>
> > +
> > +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	*/
> > +};
> > +
>
> Does POSIX mandate that these have to be 'long'? If you can change them
> all to any of 'int', '__s32' or '__s64', the handlers for 32 bit system
> call emulation on 64 bit machines will get a lot simpler because the
> 32 bit user structures are then identical to the 64 bit ones.
>
Yes, POSIX defines it to longs. And quess that compability issues should
be handled in kernel?

Krzysztof Benedyczak

  reply	other threads:[~2004-02-20 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20 13:55 [RFC][PATCH] 2/6 POSIX message queues Arnd Bergmann
2004-02-20 18:11 ` Krzysztof Benedyczak [this message]
2004-02-22 12:23   ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2004-02-22 15:12 Manfred Spraul
2004-02-19 14:28 Krzysztof Benedyczak
2004-02-19 14:53 ` Christoph Hellwig
2004-02-19 19:07   ` Sam Ravnborg
2004-02-19 19:44     ` Manfred Spraul

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=Pine.GSO.4.58.0402201848380.10845@Juliusz \
    --to=golbi@mat.uni.torun.pl \
    --cc=arnd@arndb.de \
    --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