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: Mon, 1 Nov 1999 09:00:15 -0800 (PST) [thread overview]
Message-ID: <199911011700.JAA70685@google.engr.sgi.com> (raw)
In-Reply-To: <qwwaeoyk0qi.fsf@sap.com> from "Christoph Rohland" at Nov 1, 99 10:41:25 am
>
> Hi Kanoj,
>
> This is probably breaking user space applications since shmid_ds is
> shared with user space in shmctl(2). On 32bit machines this does not
> matter, since sizeof(int) == sizeof(size_t), but on 64bit this will
> break.
>
> How do we handle this?
Unfortunately, I don't think we can prevent this 64bit ABI breakage, if
we want to conform to the single unix spec on those platforms. Its
probably a good idea to have the ia64 port be SUS compliant, even though
sparc64/alpha are currently not.
If it is really important to preserve the 64bit ABI, there's one more
alternative: preserve the shmget() api/abi on the old 64bit platforms, but
be compliant on the 32 bit ones and newer 64 bit ones (mips64/ia64). This
is not the cleanest solution, but can be done with a little header file
reorganization in include/linux/shm.h and include/linux/shmparam.h.
Linus has put this patch into pre-25, lets talk if it is important to
do the above ... it shouldn't take me more than a couple of hours to
do it, if we so decided.
Thanks.
Kanoj
>
> Greetings
> Christoph
>
> kanoj@google.engr.sgi.com (Kanoj Sarcar) writes:
>
> > Linus,
> >
> > Per our previous discussion, this is the patch to change the shmget()
> > api to permit larger shm segments (now that larger user address spaces,
> > as well as large memory machines are possible).
> >
> > Note that I have defined shmget() as
> > shmget(key_t, size_t, int)
> > instead of as
> > shmget(key_t, unsigned int, int)
> > or as
> > shmget(key_t, unsigned long, int).
> >
> > This is because the single unix spec sets down the first definition
> > (http://www.opengroup.org/onlinepubs/007908799/xsh/shmget.html).
> > This becomes interesting, because size_t is of different sizes on
> > different architectures, so the shmfs code has to do careful formatting.
> > (This logic is also probably needed in the ipcs command).
> >
> > Let me know if the patch looks okay.
> >
> > Thanks.
> >
> > 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-01 17:00 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 [this message]
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
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=199911011700.JAA70685@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