From: Kilobug <kilobug@freesurf.fr>
To: lkm <linux-kernel@vger.kernel.org>
Subject: Very big shm area
Date: Sun, 02 Jun 2002 19:21:21 +0200 [thread overview]
Message-ID: <3CFA5411.3030600@freesurf.fr> (raw)
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,
--
** Gael Le Mignot "Kilobug", Ing3 EPITA - http://kilobug.free.fr **
Home Mail : kilobug@freesurf.fr Work Mail : le-mig_g@epita.fr
GSM : 06.71.47.18.22 (in France) ICQ UIN : 7299959
Fingerprint : 1F2C 9804 7505 79DF 95E6 7323 B66B F67B 7103 C5DA
"Software is like sex it's better when it's free.", Linus Torvalds
next reply other threads:[~2002-06-02 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 17:21 Kilobug [this message]
2002-06-02 18:28 ` Very big shm area Austin Gonyou
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=3CFA5411.3030600@freesurf.fr \
--to=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