public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Krzysztof Benedyczak <golbi@mat.uni.torun.pl>
Cc: linux-kernel@vger.kernel.org, Urlich Drepper <drepper@redhat.com>,
	Michal Wronski <wrona@mat.uni.torun.pl>
Subject: Re: [PATCH] POSIX message queues - syscalls & SIGEV_THREAD
Date: Sun, 16 Nov 2003 16:35:31 +0100	[thread overview]
Message-ID: <3FB79943.70902@colorfullife.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0311161546260.25475@Juliusz>

Krzysztof Benedyczak wrote:

>+
>+/proc/fs/mqueue/max_queues  is  a  read/write  file  for  setting/getting  the
>+maximum number of message queues allowed on the system.
>+
>
Why did you add your own proc file, instead of a sysctl entry?

>+#define MQ_MAXMSG 	40	/* max number of messages in each queue */
>  
>
In the long run, this should be run time configurable. For now it 
doesn't matter, but think about that when chosing algorithms.

>+#define MQ_MAXSYSSIZE	1048576	/* max size that all m.q. can have together */
>
Dito: we must try to avoid global counters - they limit the scalability.

>+static int wq_sleep(struct mqueue_inode_info *info, int sr,
>+		    signed long timeout, struct ext_wait_queue *wq_ptr)
>+{
>
[snip]

>+		if ((current->pid == (list_entry(info->e_wait_q[sr].list.prev, struct ext_wait_queue, list))->task->pid)
>
Why current->pid? "current == ...->task" is sufficient.

>diff -urN 2.6.0-test9-orig/ipc/msg.c 2.6.0-test9-patched/ipc/msg.c
>--- 2.6.0-test9-orig/ipc/msg.c	2003-11-07 17:07:13.000000000 +0100
>+++ 2.6.0-test9-patched/ipc/msg.c	2003-11-07 18:30:17.000000000 +0100
>
>[snip: move load_msg, free_msg to util.c]
>
Could you split that into a separate patch?

--
    Manfred


  reply	other threads:[~2003-11-16 15:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-16 14:57 [PATCH] POSIX message queues - syscalls & SIGEV_THREAD Krzysztof Benedyczak
2003-11-16 15:35 ` Manfred Spraul [this message]
2003-11-17 13:57   ` Krzysztof Benedyczak
2003-11-17  6:48 ` Jamie Lokier
2003-11-17 14:58   ` Krzysztof Benedyczak
2003-11-17 15:33     ` Jamie Lokier
2003-11-17 19:18       ` Ulrich Drepper
2003-11-17 21:13         ` Jamie Lokier
2003-11-18 12:20       ` Krzysztof Benedyczak
2003-11-18 12:47         ` Jamie Lokier
2003-11-21 11:40           ` Krzysztof Benedyczak
2003-11-17 19:07     ` Ulrich Drepper
2003-11-17 21:14       ` Jamie Lokier
2003-11-17 21:30         ` Randy.Dunlap

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=3FB79943.70902@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=drepper@redhat.com \
    --cc=golbi@mat.uni.torun.pl \
    --cc=linux-kernel@vger.kernel.org \
    --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