From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: Christoph Rohland <hans-christoph.rohland@sap.com>
Cc: torvalds@transmeta.com, linux-mm@kvack.org
Subject: Re: [PATCH] kanoj-mm21-2.3.23 alow larger sizes to shmget()
Date: Tue, 2 Nov 1999 13:56:35 -0800 (PST) [thread overview]
Message-ID: <199911022156.NAA15762@google.engr.sgi.com> (raw)
In-Reply-To: <qww1za8in4z.fsf@sap.com> from "Christoph Rohland" at Nov 2, 99 10:45:00 pm
> > The clean up code is similar to what I posted at
> >
> > http://humbolt.geo.uu.nl/lists/linux-mm/1999-06/msg00071.html
> >
> > previously. Although, I would point out that SHMMAX probably belongs
> > to the asm/* header file (specially, with the size_t size parameter
> > to shmget()).
>
> Why should we make it arch dependend if we can tune it at runtime?
>
Probably 95% of people who run Linux have no idea what /proc/sys/kernel/shmmax
is, and end up recompiling the kernel with a bumped up SHMMAX, if they find
SHMMAX too low for their app. On sparc64/alpha and yet to come mips64/ia64,
SHMMAX can be pretty huge, compared to the ia32 0x2000000. Think out
of the box, and you will see that keeping SHMMAX asm dependent will work
better for most people ...
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-02 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-28 22:04 Kanoj Sarcar
1999-11-01 9:41 ` Christoph Rohland
1999-11-01 17:00 ` Kanoj Sarcar
1999-11-02 9:54 ` Christoph Rohland
1999-11-02 21:24 ` Kanoj Sarcar
1999-11-02 21:45 ` Christoph Rohland
1999-11-02 21:56 ` Kanoj Sarcar [this message]
1999-11-02 22:09 ` Christoph Rohland
1999-11-03 9:06 ` 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=199911022156.NAA15762@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=hans-christoph.rohland@sap.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@transmeta.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