linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 1/5] powerpc: consolidate feature fixup code
Date: Sat, 14 Oct 2006 08:36:46 +1000	[thread overview]
Message-ID: <1160779006.4792.269.camel@localhost.localdomain> (raw)
In-Reply-To: <20061013115457.7b36a7c3@localhost.localdomain>


> You can advance the pointer with L1_CACHE_BYTES/sizeof(int) per
> iteration in the second loop here.

Yeah, I suppose so. Though I'm not 100% confident we get L1_CACHE_BYTES
on all cpus, for example, PA6T is 64 bytes ;) We could use
cur_cpu_spec->icache_bsize but that would involve ugly RELOC's to get it
right on 32 bits. I decided not to care for now.

Ben.

  reply	other threads:[~2006-10-13 22:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13  8:04 [PATCH 1/5] powerpc: consolidate feature fixup code Benjamin Herrenschmidt
2006-10-13 16:54 ` Olof Johansson
2006-10-13 22:36   ` Benjamin Herrenschmidt [this message]
2006-10-14  2:01     ` Olof Johansson
2006-10-14  1:42   ` Stephen Rothwell
2006-10-14  1:58     ` Olof Johansson
2006-10-14  2:11 ` Olof Johansson
2006-10-16  4:51 ` Benjamin Herrenschmidt
2006-10-16  6:25   ` [PATCH 1/5] powerpc: consolidate feature fixup code #2 Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2006-10-20  1:47 [PATCH 1/5] powerpc: consolidate feature fixup code Benjamin Herrenschmidt
2006-10-20  2:00 ` Olof Johansson
2006-10-23 10:40 ` Paul Mackerras
2006-10-23 21:12   ` Benjamin Herrenschmidt

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=1160779006.4792.269.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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;
as well as URLs for NNTP newsgroup(s).