linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linuxppc-dev@ozlabs.org
Subject: dcbz not used on ppc64?
Date: Mon, 03 Jan 2005 16:54:17 -0600	[thread overview]
Message-ID: <41D9CD19.50207@nortelnetworks.com> (raw)


I ran into some issues with the use of the dcbz instruction in the 
kernel for ppc32.  I'm now looking at porting our work to ppc64, and 
when I looked around a bit, I found that the dcbz instruction doesn't 
appear to be used in ppc64.

This leads me to ask:

1) Is it in fact true that ppc64 does not use dcbz in the kernel?
2) If so, why not?  Presumably it would be a win in some cases, 
otherwise they wouldn't be using it in ppc32.  Is there some other 
factore in play for ppc64?

Thanks,

Chris

             reply	other threads:[~2005-01-03 22:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-03 22:54 Chris Friesen [this message]
2005-01-03 22:58 ` dcbz not used on ppc64? Anton Blanchard
2005-01-03 23:34   ` Chris Friesen
2005-01-04  3:16     ` Anton Blanchard

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=41D9CD19.50207@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).