public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Solofo.Ramangalahy@bull.net
Cc: linux-kernel@vger.kernel.org, Matt Helsley <matthltc@us.ibm.com>,
	Mingming Cao <cmm@us.ibm.com>,
	Nadia Derbey <Nadia.Derbey@bull.net>,
	Yasunori Goto <y-goto@jp.fujitsu.com>
Subject: Re: [RFC -mm 0/6] sysv ipc: scale msgmnb with the number of cpus
Date: Sat, 07 Jun 2008 16:38:10 +0200	[thread overview]
Message-ID: <484A9D52.2020703@colorfullife.com> (raw)
In-Reply-To: <20080605145712.116223941@bull.net>>

Solofo.Ramangalahy@bull.net wrote:
> The size in bytes of a SysV IPC message queue, msgmnb, is too small
> for large machines, but we don't want to bloat small machines
>
> Several methods are used already to modify (mainly increase) msgmnb:
> . distribution specific patch
> . system wide sysctl.conf
> . application specific tuning via /proc/sys/kernel/msgmnb
>
>   
Which distributions use a patch?

The whole configuration can be done from user space, thus I assumed that 
a sysctl.conf value (or in the worst case: a dbus/hal daemon that 
updates /proc/sys/kernel/msgnmb) could do the job.

--
    Manfred

       reply	other threads:[~2008-06-07 14:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080605145712.116223941@bull.net>
2008-06-07 14:38 ` Manfred Spraul [this message]
2008-06-08  7:19   ` [RFC -mm 0/6] sysv ipc: scale msgmnb with the number of cpus Solofo.Ramangalahy
2008-06-23 13:15   ` Solofo.Ramangalahy
2008-06-24 18:00     ` Manfred Spraul
2008-06-25  6:18       ` Solofo.Ramangalahy
2008-06-25 10:12       ` Nadia Derbey
2008-06-06  6:09 Solofo.Ramangalahy
2008-06-06  8:23 ` Nick Piggin
2008-06-06 10:20   ` Solofo.Ramangalahy
2008-06-10  6:56 ` Nadia Derbey

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=484A9D52.2020703@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=Nadia.Derbey@bull.net \
    --cc=Solofo.Ramangalahy@bull.net \
    --cc=cmm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthltc@us.ibm.com \
    --cc=y-goto@jp.fujitsu.com \
    /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