All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: gregfe <gregfe2002@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Implementation of POSIX mqueues in Linux 2.6
Date: Fri, 3 Aug 2007 06:23:25 -0400	[thread overview]
Message-ID: <20070803102325.GY2063@devserv.devel.redhat.com> (raw)
In-Reply-To: <76026.87188.qm@web26709.mail.ukl.yahoo.com>

On Fri, Aug 03, 2007 at 09:59:32AM +0000, gregfe wrote:
> I find little documentation on the actual implementation of POSIX message
> queues in Linux, and need some advise. In particular, I am wondering
> whether it supports inter-process *and* inter-thread communication, and if

Not sure what exactly you mean by inter-thread communication, whether
communication between threads within one process or between threads from
different processes.  You can use mq_* for either, except that mq_notify
registered signal notification is sent to the process that called mq_notify,
not thread (and for SIGEV_THREAD a new thread is created).

Though of course for communication between threads within one process
mq_* is a huge overkill.

> On more thing: kernel's "make menuconfig" of
> version 2.6.11 says :
> 
> >> To use this feature you will also need mqueue library, available
> 
> >> from <... a URL ... to M. Wronski's and K. Benedyczak's home page>"
> 
> Is it still up to date ?

No, glibc supports mq_* APIs for more than 3 years now.

	Jakub

      reply	other threads:[~2007-08-03 10:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03  9:59 Implementation of POSIX mqueues in Linux 2.6 gregfe
2007-08-03 10:23 ` Jakub Jelinek [this message]

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=20070803102325.GY2063@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=gregfe2002@yahoo.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.