Re: 64-bit shm: abi problems

Kanoj Sarcar (kanoj@google.engr.sgi.com)
Tue, 14 Dec 1999 15:40:33 -0800 (PST)

>
> On Tue, Dec 14, 1999 at 02:52:09PM -0800, Kanoj Sarcar wrote:
> > - .quad sys_shmctl /* 210 */
> > + .quad sys_shmctlold /* 210 */
> > .quad sys_shmdt
> > .quad sys_shmget
> > .quad alpha_ni_syscall
> > @@ -1149,3 +1149,4 @@
> > .quad sys_sendfile /* 370 */
> > .quad sys_setresgid
> > .quad sys_getresgid
> > + .quad sys_shmctl
>
> Why in the world is a new shmctl syscall being added?

This is just a proposal for fixing the shm ABI breakage.
Read the lkm subject "64-bit shm: abi problems" to see
the history. A couple of people are hard at work on this ...

>
> Yes I see someone thought it would be a keen idea to
> change shm_segsz to size_t from int. Why? I'm quite

Because SUS demands it. And because having a 2Gb limit
on a 64bit platform (specially on upcoming ia64) is rather
limiting.

Kanoj

> happy with a 2G limit; you should have been using mmap
> well before that anyway.
>
>
> r~
>

-
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/