From: "J.A. Magallon" <jamagallon@able.es>
To: Andrew Morton <akpm@digeo.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
"David S. Miller" <davem@redhat.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC][PATCH] net drivers and cache alignment
Date: Sun, 8 Dec 2002 00:37:46 +0100 [thread overview]
Message-ID: <20021207233745.GE3183@werewolf.able.es> (raw)
In-Reply-To: <3DF2844C.F9216283@digeo.com>; from akpm@digeo.com on Sun, Dec 08, 2002 at 00:29:16 +0100
On 2002.12.08 Andrew Morton wrote:
>Jeff Garzik wrote:
>>
>> David S. Miller wrote:
>> > Can't the cacheline_aligned attribute be applied to individual
>> > struct members? I remember doing this for thread_struct on
>> > sparc ages ago.
>>
>> Looks like it from the 2.4 processor.h code.
>>
>> Attached is cut #2. Thanks for all the near-instant feedback so far :)
>> Andrew, does the attached still need padding on SMP?
>
What do you all think about this:
#include <stdio.h>
#define CACHE_LINE_SIZE 128
#define ____cacheline_aligned __attribute__((__aligned__(CACHE_LINE_SIZE)))
#define __cacheline_start struct { } ____cacheline_aligned;
#define offsetof(t, m) ((int)(&((t *)0)->m))
struct S {
__cacheline_start
int x;
__cacheline_start
int y;
int z;
};
int main()
{
struct S s;
printf("%d\n",sizeof(struct S));
printf("%d\n",offsetof(struct S,x));
printf("%d\n",offsetof(struct S,y));
printf("%d\n",offsetof(struct S,z));
}
werewolf:~> vi kk.c
werewolf:~> kk
256
0
128
132
So you don't have to modify any field, just put __cacheline_start where
needed ? (and does not add any extra sizeof(int) overhead).
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.1 (Cooker) for i586
Linux 2.4.20-jam1 (gcc 3.2 (Mandrake Linux 9.1 3.2-4mdk))
next prev parent reply other threads:[~2002-12-07 23:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 22:37 [RFC][PATCH] net drivers and cache alignment Jeff Garzik
2002-12-07 22:40 ` David S. Miller
2002-12-07 22:46 ` Jeff Garzik
2002-12-07 23:06 ` Jeff Garzik
2002-12-07 23:29 ` Andrew Morton
2002-12-07 23:30 ` David S. Miller
2002-12-07 23:42 ` Andrew Morton
2002-12-07 23:51 ` Andrew Morton
2002-12-15 18:31 ` Jes Sorensen
2002-12-08 20:00 ` David S. Miller
2002-12-07 23:36 ` Jeff Garzik
2002-12-07 23:37 ` J.A. Magallon [this message]
2002-12-07 23:42 ` Jeff Garzik
2002-12-07 23:45 ` Andrew Morton
2002-12-07 23:52 ` J.A. Magallon
2002-12-08 1:14 ` Daniel Jacobowitz
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=20021207233745.GE3183@werewolf.able.es \
--to=jamagallon@able.es \
--cc=akpm@digeo.com \
--cc=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.