From: Peter Waechtler <pwaechtler@mac.com>
To: Michal Wronski <wrona@mat.uni.torun.pl>
Cc: linux-kernel@vger.kernel.org,
Krzysztof Benedyczak <golbi@mat.uni.torun.pl>,
"Gustafson, Geoffrey R" <geoffrey.r.gustafson@intel.com>,
"Abbas, Mohamed" <mohamed.abbas@intel.com>
Subject: Re: [PATCH] unified SysV and POSIX mqueues - complete rewrite
Date: Wed, 13 Nov 2002 23:25:24 +0100 [thread overview]
Message-ID: <3DD2D154.AB45F0CD@mac.com> (raw)
In-Reply-To: Pine.LNX.4.44.0211131555530.9870-100000@Leon
Michal Wronski schrieb:
>
> > The interface boils down to 7 new syscalls (for now just i386):
> > - sys_mq_open
> > - sys_mq_unlink
> > - sys_mq_timedsend
> > - sys_mq_timedreceive
> > ...
>
> Why add a new syscalls?? It's better to do this via ioctl's
>
Hmh, there was some discussion concluding that ioctl is
"bad taste from hell". Syscalls are considered cleaner
and less error prone.
> I suggest doing this independently to SysV IPC
I just reused the message storage code.
>
> > userspace lib and test progs are on
> > http://homepage.mac.com/pwaechtler/linux/mqueue/
>
> "We're sorry, but we can't find the HomePage you've requested."
>
Yes, I'm also sorry ;-)
a wget http://homepage.mac.com/pwaechtler/linux/mqueue.tgz
should work. (i'm not comfortable with my own homepage, shame on me :)
> > +#ifndef _LINUX_MQUEUE_H
> > +#define _LINUX_MQUEUE_H
> > +
> > +#define MQ_MAXMSG 40 /* max number of messages in each queue */
> > +#define MQ_MAXSYSSIZE 1048576 /* max size that all m.q. can have
> > together
> > */
> > +#define MQ_PRIO_MAX 10000 /* max priority */
>
> I see that you've read our sources....
>
Yes, indeed. I also evaluated your implementation and the one from Jakub.
First I thought: hey cool, they use binary trees for the messages - but
no: you use trees to keep track which process uses which queue.
Your code carries a lot of baggage.. the VFS can do all this for you/me
> We (K. Benedyczak with me) are currently working on new implementation of
> mqueues. It's very similar to yours (filesystem, without new syscalls) and
> it's almost done. Maybe we should collaborate??
>
Yes, why not. But to be honest my implementation is already "full featured".
Perhaps one could handle the message lists more effectively ..
I'm currently trying to do some performance measurements with NPTL and the
userspace implementation I have.
next prev parent reply other threads:[~2002-11-13 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDC461A30AC4D511ADE10002A5072CAD04C70992@orsmsx119.jf.intel.com>
2002-11-13 15:10 ` [PATCH] unified SysV and POSIX mqueues - complete rewrite Michal Wronski
2002-11-13 22:25 ` Peter Waechtler [this message]
2002-11-19 11:28 ` Krzysztof Benedyczak
2002-11-19 16:42 ` Peter Waechtler
2002-11-24 11:55 ` Michal Wronski
2002-11-26 9:12 ` Michal Wronski
2002-11-26 11:16 ` Peter Waechtler
2002-11-24 23:05 Peter Waechtler
[not found] ` <3DE15F9E.A585E26F@digeo.com>
2002-11-25 1:02 ` Peter Waechtler
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 19:12 Perez-Gonzalez, Inaky
2002-11-10 23:44 Peter Waechtler
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=3DD2D154.AB45F0CD@mac.com \
--to=pwaechtler@mac.com \
--cc=geoffrey.r.gustafson@intel.com \
--cc=golbi@mat.uni.torun.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mohamed.abbas@intel.com \
--cc=wrona@mat.uni.torun.pl \
/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