From: William Lee Irwin III <wli@holomorphy.com>
To: Arvind Kandhare <arvind.kan@wipro.com>
Cc: Manfred Spraul <manfred@colorfullife.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"indou.takao" <indou.takao@jp.fujitsu.com>, rml <rml@tech9.net>,
Dave Jones <davej@suse.de>,
roystgnr@owlnet.rice.edu, garagan@borg.cs.dal.ca
Subject: Re: Changing SEMVMX to a tunable parameter
Date: Thu, 29 May 2003 03:34:14 -0700 [thread overview]
Message-ID: <20030529103414.GY8978@holomorphy.com> (raw)
In-Reply-To: <3ED5DE49.5CA79049@wipro.com>
On Thu, May 29, 2003 at 03:47:45PM +0530, Arvind Kandhare wrote:
> 1. Most of the IPC parameters (e.g. msgmni, msgmax,
> msgmnb , shmmni, shmmax) are tunables.
> (Please refer :
> http://web.gnu.walfield.org/mail-archive/linux-kernel-digest/1999-November/0020.html)
> Was there any specific reason why semvmx was not made a tunable with the
> above set??
> 2. By having semvmx as tunable, administrator gets more flexibility
> in controlling the resource usage on the system:
> a. By increasing this, it is possible to allow more
> processes to use the system resources controlled by a
> semaphore concurrently.
> b. By decreasing this, the number of processes
> using the system resources controlled by a semaphore
> concurrently can be limited.
Why not just implement it and let us take a look at it? It shouldn't be
that far out. Nothing wrong with fully dynamic tuning in principle,
though this stuff is pretty obscure. Just hammer it out and we'll see how
it looks.
-- wli
next prev parent reply other threads:[~2003-05-29 10:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 14:24 Changing SEMVMX to a tunable parameter Arvind Kandhare
2003-05-28 16:15 ` Manfred Spraul
2003-05-29 10:17 ` Arvind Kandhare
2003-05-29 10:34 ` William Lee Irwin III [this message]
2003-05-29 10:36 ` Manfred Spraul
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=20030529103414.GY8978@holomorphy.com \
--to=wli@holomorphy.com \
--cc=arvind.kan@wipro.com \
--cc=davej@suse.de \
--cc=garagan@borg.cs.dal.ca \
--cc=indou.takao@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=rml@tech9.net \
--cc=roystgnr@owlnet.rice.edu \
/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