From: "linux-os \(Dick Johnson\)" <linux-os@analogic.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, cr@sap.com, linux-mm@kvack.org
Subject: Re: Getting rid of SHMMAX/SHMALL ?
Date: Thu, 4 Aug 2005 07:58:45 -0400 [thread overview]
Message-ID: <Pine.LNX.4.61.0508040757220.15854@chaos.analogic.com> (raw)
In-Reply-To: <20050804113941.GP8266@wotan.suse.de>
On Thu, 4 Aug 2005, Andi Kleen wrote:
>
> I noticed that even 64bit architectures have a ridiculously low
> max limit on shared memory segments by default:
>
> #define SHMMAX 0x2000000 /* max shared seg size (bytes) */
> #define SHMMNI 4096 /* max num of segs system wide */
> #define SHMALL (SHMMAX/PAGE_SIZE*(SHMMNI/16)) /* max shm system wide (pages) */
>
> Even on 32bit architectures it is far too small and doesn't
> make much sense. Does anybody remember why we even have this limit?
>
> IMHO per process shm mappings should just be controlled by the normal
> process and global mappings with the same heuristics as tmpfs
> (by default max memory / 2 or more if shmfs is mounted with more)
> Actually I suspect databases will usually want to use more
> so it might even make sense to support max memory - 1/8*max_memory
>
> I would propose to get rid of of shmmax completely
> and only keep the old shmall sysctl for compatibility.
>
> Comments?
>
> -Andi
It doesn't seem to be used very much. Here's the `grep` of the
entire 2.6.12 source-tree:
size_t shm_ctlmax = SHMMAX;
./ipc/shm.c
(actually only bits 25..16 get used since SHMMAX is so low)
./include/asm-m68k/shm.h
KERN_SHMMAX=34, /* long: Maximum shared memory segment */
./include/linux/sysctl.h
* SHMMAX, SHMMNI and SHMALL are upper limits are defaults which can
#define SHMMAX 0x2000000 /* max shared seg size (bytes) */
#define SHMALL (SHMMAX/PAGE_SIZE*(SHMMNI/16)) /* max shm system wide (pages) */
./include/linux/shm.h
(actually only bits 25..16 get used since SHMMAX is so low)
./include/asm-h8300/shm.h
#ifndef SHMMAX
#define SHMMAX 0x003fa000
./include/asm-arm26/shmparam.h
.ctl_name = KERN_SHMMAX,
./kernel/sysctl.c
Cheers,
Dick Johnson
Penguin : Linux version 2.6.12 on an i686 machine (5537.79 BogoMips).
Warning : 98.36% of all statistics are fiction.
.
I apologize for the following. I tried to kill it with the above dot :
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@analogic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-08-04 11:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-04 11:39 Andi Kleen
2005-08-04 11:58 ` linux-os (Dick Johnson) [this message]
2005-08-04 13:19 ` Hugh Dickins
2005-08-04 13:23 ` Andi Kleen
2005-08-04 14:20 ` Matti Aarnio
2005-08-04 14:48 ` Hugh Dickins
2005-08-07 11:38 ` Alan Cox
2005-08-04 15:19 ` Andi Kleen
2005-08-04 22:49 ` Chen, Kenneth W
2005-08-04 22:54 ` Andi Kleen
2005-08-04 22:58 ` Chen, Kenneth W
2005-08-04 13:34 ` Jakob Oestergaard
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=Pine.LNX.4.61.0508040757220.15854@chaos.analogic.com \
--to=linux-os@analogic.com \
--cc=ak@suse.de \
--cc=cr@sap.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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