From: Anton Blanchard <anton@samba.org>
To: Shai Fultheim <shai@scalex86.org>
Cc: "'Andrew Morton'" <akpm@osdl.org>,
"'Linux Kernel ML'" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Alignment for CPU maps, add padding semantics
Date: Mon, 12 Jul 2004 18:39:30 +1000 [thread overview]
Message-ID: <20040712083930.GA2324@krispykreme> (raw)
In-Reply-To: <S266631AbUGKWxO/20040711225314Z+1231@vger.kernel.org>
Hi,
> The attached patch add missing alignments for CPU maps (cpu_online_map,
> node_2_cpu_mask, cpu_2_node, cpu_2_logical_apicid). It allows better
> cache-line utilization by having the most usable part of each map on
> same cache-line.
These bitmaps are pretty much readonly and 4 bytes on most machines and
this change makes them up to 128 bytes long. They are also naturally
aligned in the 4 byte case so cannot cross a cacheline boundary.
It makes much more sense to have all these readonly structures packed
together in the same cacheline.
Anton
next prev parent reply other threads:[~2004-07-12 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-11 22:53 [PATCH] Alignment for CPU maps, add padding semantics Shai Fultheim
2004-07-12 8:39 ` Anton Blanchard [this message]
[not found] <200407112253.i6BMrEws001373@fire-2.osdl.org>
2004-07-12 5:07 ` Andrew Morton
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=20040712083930.GA2324@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.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