Re: #define SHMMAX 0x2000000

Christoph Rohland (hans-christoph.rohland@sap-ag.de)
13 Nov 1998 23:35:17 +0100


alan@lxorguk.ukuu.org.uk (Alan Cox) writes:

> > I found this one in patch-2.1.128.gz:
> >
> > + #define SHMMAX 0x2000000 /* max shared seg size (bytes) */
> > + /* Try not to change the default shipped SHMMAX - people rely on it */
> > +
> >
> > This can not be true! Linux should not use segments > 32M??? We just
> > got able to use more than 128M and now we say, only 32M. I cannot
> > believe it.
>
> Look harder.
>
> Its the default for kernel builds, and the value exported to apps. It was
> set at 0x1000000 in 2.1.x before that diff. That meant 2.0 built apps
> assuming they could get 0x20000000 byet chunks blew up on 2.1.x and was
> a compatibility bug.
>
> Yes you can alter that value up to a gig or more now but the value is
> a default. Its probably also a sysctl candidate if anyone feels
> inspired

So you mean:

+ #define SHMMAX 0x2000000 /* max shared seg size (bytes) */
+ /* Try not to reduce the default shipped SHMMAX - people rely on it */
^^^^^^
That would be fine for me...

Christoph

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/