From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: Christoph Rohland <hans-christoph.rohland@sap.com>
Cc: linux-mm@kvack.org, dledford@redhat.com, ebiederm+eric@ccr.net
Subject: Re: [RFC] mapping parts of shared memory
Date: Thu, 25 Nov 1999 11:14:31 -0800 (PST) [thread overview]
Message-ID: <199911251914.LAA27659@google.engr.sgi.com> (raw)
In-Reply-To: <qww3dtuisg4.fsf@sap.com> from "Christoph Rohland" at Nov 25, 99 02:58:19 pm
>
> Hi,
>
> I was investigating for some time about the possibility to create some
> object which allows me to map and unmap parts of it it in different
> processes. This would help to take advantage of the high memory
> systems with applications like SAP R/3 which uses a small number of
> processes to server many clients. It is now limited by the available
> address space for one process.
>
Lets see if I am understanding the problem right. Currently, you may
have an ia32 box with 8G memory, unfortunately, your server can make
use of at most (say) 3G worth of shared memory. Hence, you are worried
about how to be able to use the other 5G, lets say with more server
processes.
What prevents your app from creating say 2 shm segments, each around
2.5G or so? That will let you attach in and use about 5G between 2
server processes. What have you lost with this approach that you will
get with the kernel approach?
Kanoj
--
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 prev parent reply other threads:[~1999-11-25 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-25 13:58 Christoph Rohland
1999-11-25 19:14 ` Kanoj Sarcar [this message]
1999-11-26 15:33 ` Christoph Rohland
1999-12-02 20:52 Bruno Haible
1999-12-02 21:18 ` Alexander Viro
1999-12-03 8:10 ` Christoph Rohland
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=199911251914.LAA27659@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=dledford@redhat.com \
--cc=ebiederm+eric@ccr.net \
--cc=hans-christoph.rohland@sap.com \
--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