Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Justin Carlson <carlson@sibyte.com>
To: linux-mips@oss.sgi.com
Subject: _clear_page semantics
Date: Tue, 9 Jan 2001 17:48:11 -0800	[thread overview]
Message-ID: <01010917590106.07691@plugh.sibyte.com> (raw)


Looking at the existing clear_page implementations for r4xx0, rm7k, and mips32
in the mips/ tree, I see everyone issuing cache op 0xd for the address range of
the page being cleared.

I'm wondering what the purpose is of these cache flushes...given a physically
tagged dcache, my understanding of the semantics of clear_page are that it just
zeros the page, in which case the cache ops are pointless overhead.

Especially in the mips32 case, which uses cache op 0xd, which is undefined
implementation dependent according to my mips32 spec.

Am I missing something here?

Thanks,
Justin

             reply	other threads:[~2001-01-10  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10  1:48 Justin Carlson [this message]
2001-01-10  5:03 ` _clear_page semantics Ralf Baechle
2001-01-10  8:08 ` Carsten Langgaard
2001-01-10 15:34   ` Ralf Baechle

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=01010917590106.07691@plugh.sibyte.com \
    --to=carlson@sibyte.com \
    --cc=linux-mips@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox