From: Austin Gonyou <austin@digitalroadkill.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Kilobug <kilobug@freesurf.fr>, lkm <linux-kernel@vger.kernel.org>
Subject: Re: Very big shm area
Date: 02 Jun 2002 13:44:11 -0500 [thread overview]
Message-ID: <1023043451.3021.8.camel@UberGeek> (raw)
In-Reply-To: <20020602183721.GG14918@holomorphy.com>
To get *good* performance from such a large SGA, it's best to use a -aa
kernel I've found. Either 2.4.18-aa + whatever patches, or something
similar. But there's been some fixes/changes/optimizations to the -aa
tree with regards to large memory boxes.
I'm curious though how P4 HT will play into that performance on the new
Xeons though. I'll have more to report in the next few weeks.
On Sun, 2002-06-02 at 13:37, William Lee Irwin III wrote:
> On Sun, Jun 02, 2002 at 07:21:21PM +0200, 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,
>
> ls /proc/sys/kernel/sh* and the names shouldn't be too tough from there.
> I'd be concerned about exercising this code on a virgin 2.4.17 as ISTR
> bugfixes for sysv ipc/shm cropping up in later kernel versions, though
> I can't say I've tracked this area very closely. Hopefully someone who
> does can chime in here and enlighten us both.
>
>
> Cheers,
> Bill
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2002-06-02 18:44 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
2002-06-02 18:37 ` William Lee Irwin III
2002-06-02 18:44 ` Austin Gonyou [this message]
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=1023043451.3021.8.camel@UberGeek \
--to=austin@digitalroadkill.net \
--cc=kilobug@freesurf.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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