From: Jason Froebe <jfroebe@sybase.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.rutgers.edu" <linux-kernel@vger.rutgers.edu>
Subject: Re: Shared memory segment > 1gb
Date: Wed, 27 Jan 1999 17:32:23 -0600 [thread overview]
Message-ID: <36AFA207.AB6D149E@sybase.com> (raw)
In-Reply-To: <F6D006CF40DA6D8485256706006560F5.006560A786256706@sybase.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
Jason Froebe wrote:
> Hi,
>
> I'm trying to get a shared memory segment of just under 2 gb. So
> far, I've been able to get a 893mb shared segment by altering the
> _SHM_IDX_BITS to 18 in include/asm/shmparam.h using the 2.2.0
> kernel. I'm assuming I can set the _SHM_IDX_BITS to 19 without a
> problem (more overhead though), but since this is my "working"
> computer, I don't want any surprises. is this possible without
> breaking something? I glanced at the code but didn't see any
> obvious "gotchas".
>
> Don't ask why I don't use multiple segments. It's not my
> decision.
>
> Jason
>
> - jfroebe.vcf
Hi,
I've increased the _SHM_IDX_BITS to 19 and decreased _SHM_ID_BITS to
5 with SHMMAX set to 2gb - 2*page size but it didn't help. I'm
still stuck at 893mb.
Does anyone know of how to increase the shared memory segment
further without using multiple segments?
Thanks
Jason
[-- Attachment #2: Card for Jason Froebe --]
[-- Type: text/x-vcard, Size: 339 bytes --]
begin:vcard
n:Froebe;Jason
tel;fax:773-864-7288
tel;work:1-800-8SYBASE
x-mozilla-html:TRUE
url:http://www.sybase.com
org:Sybase, Inc.;Technical Support
adr:;;8755 W. Higgins Road Suite 1000 ;Chicago;IL;60631;USA
version:2.1
email;internet:jfroebe@sybase.com
title:Technical Support Engineer
x-mozilla-cpt:;20256
fn:Jason Froebe
end:vcard
next parent reply other threads:[~1999-01-27 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F6D006CF40DA6D8485256706006560F5.006560A786256706@sybase.com>
1999-01-27 23:32 ` Jason Froebe [this message]
1999-01-27 17:50 Jason Froebe
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=36AFA207.AB6D149E@sybase.com \
--to=jfroebe@sybase.com \
--cc=linux-kernel@vger.rutgers.edu \
--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