From: Thomas Hiller <thomas.hiller@sap-ag.de>
To: Linux-MM@kvack.org, kanoj@google.engr.sgi.com
Subject: SHM implementation in 2.2.x
Date: Wed, 14 Jul 1999 17:05:21 +0200 [thread overview]
Message-ID: <378CA731.846F7580@sap-ag.de> (raw)
What are the real limits in using SHM ?
I looked through the code and are quite lost.
There seem to be a 24 bit limit in ID + IDX bits (shmparam.h). Is this
due to the fact that the other 8 bits are used for SWP_TYPE ?
What is the limit for SHMMAX and what advantage is there to leave it at
a lower limit ?
What we need are many big shared segments (say 4000 * 1 GB). Is this
possible with the current implementation ? Or what must be changed ?
Only SHM_ID_BITS and SHMMAX ?
Thanks in advance.
- Thomas
--
Thomas Hiller
Compaq Computer EMEA BV
SAP International Competence Center
LinuxLab
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-07-14 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-14 15:05 Thomas Hiller [this message]
1999-07-14 17:20 ` Kanoj Sarcar
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=378CA731.846F7580@sap-ag.de \
--to=thomas.hiller@sap-ag.de \
--cc=Linux-MM@kvack.org \
--cc=kanoj@google.engr.sgi.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