From: "Anil Kumar" <anilk@subexgroup.com>
To: "Der Herr Hofrat" <der.herr@hofr.at>, <linux-kernel@vger.kernel.org>
Subject: RE: sizeof problem in kernel modules
Date: Mon, 25 Jun 2001 10:03:38 +0530 [thread overview]
Message-ID: <NEBBIIKAMMOCGCPMPBJOOEGGCGAA.anilk@subexgroup.com> (raw)
In-Reply-To: <200106231454.f5NEsKu14812@kanga.hofr.at>
struct { short x; long y; short z; }bad_struct;
struct { long y; short x; short z; }good_struct;
I would expect both structs to be 8byte in size , or atleast the same size !
but good_struct turns out to be 8bytes and bad_struct 12 .
what am I doing wrong here ?
thx !
hofrat
///////////////////////////////////////
It's general padding performed everywhere for a 32-bit m/c. Since the short
number is considered to be of 2 bytes whereas new data should start at the
next 32 bit alignment( if the data length exceeds the padding required )
hence next 2 bytes are left as padding, so the actual struct. of your
defined structutres are as follows,
struct{
short x; /* 2- bytes */
/* again 2- bytes padding */
long y; /* 4 - bytes */
short z; /* 2 - bytes */
/* again 2 - bytes padding
}bad_struct;
struct{
long y; /* 4 - bytes */
short x; /* 2 - bytes */
short z; /* 2 - bytes */
}good_struct;
anil
prev parent reply other threads:[~2001-06-25 4:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-23 14:54 Der Herr Hofrat
2001-06-23 15:18 ` Keith Owens
2001-06-23 15:30 ` Russell King
2001-06-24 1:56 ` Richard B. Johnson
2001-06-24 2:12 ` Keith Owens
2001-06-24 2:43 ` Richard B. Johnson
2001-06-24 16:07 ` Lieven Marchand
2001-06-24 16:11 ` frank
2001-06-25 0:26 ` Michael Meissner
2001-06-25 11:32 ` Richard B. Johnson
2001-06-25 13:38 ` Alan Shutko
2001-06-25 14:49 ` Richard B. Johnson
2001-06-25 19:19 ` Alan Shutko
2001-06-25 13:59 ` Alan Shutko
2001-06-25 15:07 ` Andreas Schwab
2001-06-25 21:25 ` Horst von Brand
2001-06-25 20:43 ` Michael Meissner
2001-06-25 4:33 ` Anil Kumar [this message]
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=NEBBIIKAMMOCGCPMPBJOOEGGCGAA.anilk@subexgroup.com \
--to=anilk@subexgroup.com \
--cc=der.herr@hofr.at \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®