From: Matthew Wilcox <willy@debian.org>
To: linux-ia64@vger.kernel.org
Subject: Re: shared memory between 32bit & 64bit applications
Date: Mon, 03 May 2004 13:25:11 +0000 [thread overview]
Message-ID: <20040503132511.GJ2281@parcelfarce.linux.theplanet.co.uk> (raw)
On Mon, May 03, 2004 at 06:46:09PM +0530, ARADHYA, CHINMAYA TM (STSD) wrote:
> The information which is held in the shared memory
> is interpreted as in the structure
> typedef struct shmtest
> {
> int req;
> long long id;
> int abc;
> }shmtest_t;
>
> The 64 bit application fills in {1,5,5} in the shared
> memory and when I access these values from a 32 bit application
> I get it as {1,21474836480,0}. I guess this is due to
> switch of lower and upper significant bytes.
Nope. You're being bitten by different struct padding rules.
#include <stdio.h>
struct foo {
int req;
long long id;
int abc;
};
int main(void) { return printf("%d\n", sizeof(struct foo)); }
On ia64, this prints 24; on i386 it prints 16.
You could declare it __attribute__((packed)) or you could reorder the
elements in the struct to put the largest elements first.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next reply other threads:[~2004-05-03 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 13:25 Matthew Wilcox [this message]
2004-05-03 13:28 ` shared memory between 32bit & 64bit applications ARADHYA, CHINMAYA TM (STSD)
2004-05-03 15:07 ` Grant Grundler
2004-05-04 2:04 ` Keith Owens
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=20040503132511.GJ2281@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=linux-ia64@vger.kernel.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