mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: christoph <christoph@scalex86.org>
Cc: Andi Kleen <ak@suse.de>,
	akpm@osdl.org, linux-kernel@vger.kernel.org, shai@scalex86.org
Subject: Re: [PATCH] Move some variables into the "most_readonly" section??
Date: Wed, 15 Jun 2005 01:04:11 +0200	[thread overview]
Message-ID: <20050614230411.GU11898@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.62.0506141551350.3676@ScMPusgw>

On Tue, Jun 14, 2005 at 03:54:24PM -0700, christoph wrote:
> On Wed, 8 Jun 2005, Andi Kleen wrote:
> 
> > However this means __cacheline_aligned_mostly_readonly doesnt make much
> > sense since there is no need for alignment in read only. How about
> > replacing it with a __mostly_readonly that doesnt align and remove
> > __cacheline_aligned_mostly_readonly? 
> 
> Hmm. No. The bigger cpu maps may benefit from cacheline alignment for 
> even for read access. 

Why? Can you please explain that. It doesn't make sense to me.

Any read only cache line should be freely shareable over all caches.

Thanks.

-Andi

  reply	other threads:[~2005-06-14 23:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-07 19:58 christoph
2005-06-08 13:18 ` Andi Kleen
2005-06-14 22:54   ` christoph
2005-06-14 23:04     ` Andi Kleen [this message]
2005-06-14 23:17       ` Christoph Lameter
2005-06-14 23:19         ` Andi Kleen
2005-06-14 23:27           ` Christoph Lameter
2005-06-14 23:54             ` Andi Kleen
2005-06-14 23:23     ` Andrew Morton
2005-06-14 23:46       ` christoph
2005-06-14 23:58         ` Andrew Morton
2005-06-15  0:05           ` christoph
2005-06-15  0:16             ` Andrew Morton
2005-06-15  0:41               ` Andi Kleen
2005-06-17 13:55                 ` Anton Blanchard
2005-06-27 23:17                   ` christoph
2005-06-15  0:18           ` Nick Piggin

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=20050614230411.GU11898@wotan.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=christoph@scalex86.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
all inboxes | Powered by JetHome®