From: Austin Gonyou <austin@digitalroadkill.net>
To: Kilobug <kilobug@freesurf.fr>
Cc: lkm <linux-kernel@vger.kernel.org>
Subject: Re: Very big shm area
Date: 02 Jun 2002 13:28:48 -0500 [thread overview]
Message-ID: <1023042528.3021.1.camel@UberGeek> (raw)
In-Reply-To: <3CFA5411.3030600@freesurf.fr>
I run a Dell 6450 with 8GB ram and a 4GB SHMMAX. You can set the
parameter any time through sysctl if you have it enabled, or you can
hardcode it per the Oracle/DB2 Docs if you wish.
Austin
On Sun, 2002-06-02 at 12:21, Kilobug wrote:
> Hello,
> I wanted to know if it is possible to have a very big system V shared
> memory segment (say about 1Gb) ?
>
> I've quickly looked into the source code of shm.c and shm.h in ipc/ and
> I've read the following:
> /*
> * SHMMAX, SHMMNI and SHMALL are upper limits are defaults which can
> * be increased by sysctl
> */
>
> But how far is it possible to increase them ? And which sysctl must be
> done ?
>
> Thank you for answering,
next prev parent reply other threads:[~2002-06-02 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 17:21 Very big shm area Kilobug
2002-06-02 18:28 ` Austin Gonyou [this message]
2002-06-02 18:37 ` William Lee Irwin III
2002-06-02 18:44 ` Austin Gonyou
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=1023042528.3021.1.camel@UberGeek \
--to=austin@digitalroadkill.net \
--cc=kilobug@freesurf.fr \
--cc=linux-kernel@vger.kernel.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