From: Ulf Carlsson <ulfc@thepuffingroup.com>
To: Linux SGI <linux@cthulhu.engr.sgi.com>
Subject: Indy SC bug
Date: Mon, 10 May 1999 20:56:40 +0200 [thread overview]
Message-ID: <19990510205640.A11145@thepuffingroup.com> (raw)
Hi all,
I've found a silly bug in the R4600SC caching routines. It wiped the whole cache
at wrap arounds even if you just tried to write back two cache lines (for
example the last cache line and the first cache line).
I can't understand how this bug has lasted so long in the kernel. Well, now that
I've sorted it out, your R4600SC machine be A LOT faster.
- Ulf
reply other threads:[~1999-05-10 17:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19990510205640.A11145@thepuffingroup.com \
--to=ulfc@thepuffingroup.com \
--cc=linux@cthulhu.engr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.