From: Chris Wright <chrisw@osdl.org>
To: Martijn Sipkema <m.j.w.sipkema@student.tudelft.nl>
Cc: Jakub Jelinek <jakub@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: POSIX message queues should not allocate memory on send
Date: Fri, 14 May 2004 09:58:30 -0700 [thread overview]
Message-ID: <20040514095830.F22989@build.pdx.osdl.net> (raw)
In-Reply-To: <000601c439a3$f793af40$161b14ac@boromir>; from m.j.w.sipkema@student.tudelft.nl on Fri, May 14, 2004 at 12:09:46PM +0100
* Martijn Sipkema (m.j.w.sipkema@student.tudelft.nl) wrote:
> You are correct; defaults are indeed needed. The current default value
> for mq_msgsize seems rather large considering that mq_msgsize*mq_maxmsg
> bytes will have to be allocated on queue creation. If variable sized large
> payload messages are needed one might consider using shared memory in
> combination with a message queue.
The defaults have been reduced in -mm tree which should make it to
mainline in relative near future.
#define DFLT_MSGMAX 10 /* max number of messages in each queue */
#define DFLT_MSGSIZEMAX 8192 /* max message size */
> My main point was that mq_send()/mq_timedsend() may not return ENOMEM
> and I am positive I did not misread the standard on that.
I'm not sure it's that clear, however, we somewhat adhered to this
principle when adding rlimits to mqueues, so rlimit checks are enforced
on mq_open() as if whole thing was pre-allocated.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2004-05-14 16:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 10:30 POSIX message queues should not allocate memory on send Martijn Sipkema
2004-05-14 9:51 ` Jakub Jelinek
2004-05-14 11:09 ` Martijn Sipkema
2004-05-14 10:40 ` Jakub Jelinek
2004-05-14 12:42 ` Martijn Sipkema
2004-05-14 15:57 ` Ulrich Drepper
2004-08-15 0:12 ` Martijn Sipkema
2004-05-14 16:58 ` Chris Wright [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=20040514095830.F22989@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.j.w.sipkema@student.tudelft.nl \
/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