public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Alex Riesen <fork0@users.sourceforge.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: POSIX message queues, libmqueue: mq_open, mq_unlink
Date: Sat, 17 Apr 2004 12:49:08 +0200	[thread overview]
Message-ID: <40810BA4.50803@colorfullife.com> (raw)

Alex wrote:

>Ok. It's just that every provider of the _kernel_ interface to user
>space has now to take care of being posix-compliant. Write the code for
>checks, iow. That is not the case for "open", for instance.
>And besides, with the patch applied the kernel is also posix compliant,
>isn't it?
>
No. E.g. mq_notify(,&{.sigev_notify=SIGEV_THREAD) cannot be implemented 
in kernel space. And sys_mq_getsetattr isn't posix compliant either - 
the user space library must implement mq_getattr and mq_setattr on top 
of the kernel API.
The kernel API was designed to be simple and flexible. Perhaps we want 
to extend the kernel implementation in the future, and then a leading 
slash could be used to indicate that we are using the new features.

--
    Manfred


             reply	other threads:[~2004-04-17 10:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17 10:49 Manfred Spraul [this message]
2004-04-17 11:16 ` POSIX message queues, libmqueue: mq_open, mq_unlink Alex Riesen
  -- strict thread matches above, loose matches on Subject: below --
2004-04-16  8:11 Alex Riesen
2004-04-16 16:13 ` Ulrich Drepper
2004-04-16 21:38   ` Alex Riesen
2004-04-16 22:17     ` Ulrich Drepper
2004-04-16 22:22     ` Chris Wright
2004-04-16 23:43       ` Alex Riesen
2004-04-16 23:56         ` Chris Wright
2004-04-17  8:20           ` Alex Riesen

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=40810BA4.50803@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=fork0@users.sourceforge.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