From: Frank Rowand <frank_rowand@hp.com>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] depi?
Date: Wed, 17 Nov 1999 15:02:38 -0800 [thread overview]
Message-ID: <3833340E.59C7BDB4@hp.com> (raw)
In-Reply-To: 19991117230531.D10209@mathe.stud.uni-erlangen.de
Philipp Rumpf wrote:
< stuff deleted - I don't need to argue, my face is already turning blue... >
> What I really want to know is which algorithm do recent CPUs use to get the
> cache bank index / cache tag.
< stuff deleted >
> [note: what follows is what I think is a proof we can do what I want to do.
> It is very likely to contain formal/grammatical mistakes but I think it should
> be valid nontheless].
>
> The Rules
<stuff deleted >
> Any mistakes to point out ? Misunderstandments in the specification ? Other-
> wise could the specification please get fixed ?
>
> Philipp Rumpf
I didn't bother reading the proof, so no arguments about it. I already thought
through what is probably a similar proof for myself.
The problem is that no matter how obvious it is to us software folks that it
would be braindead, illogical, or nearly impossible for the hardware to
behave in strange ways, the hardware folks are incredibly devious at making
the hardware more effective, within the constraints of the architecture
(and, on occasion, outside the constraints). This results in behaviour that
may seem unreasonable to a software person.
***** I attempt to code within the ARCHITECTURE, not to implement what
specific hardware implementations let me get away with. That way I don't
get burnt by the creative hardware engineers, who might be pushing the
envelope. *****
-Frank
next prev parent reply other threads:[~1999-11-17 23:01 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-15 8:08 [parisc-linux] depi? Alex deVries
1999-11-15 7:24 ` Jeffrey A Law
1999-11-15 7:36 ` Stan Sieler
1999-11-15 8:25 ` Philipp Rumpf
1999-11-15 23:14 ` Frank Rowand
1999-11-16 0:26 ` John David Anglin
1999-11-16 12:39 ` Matthew Wilcox
1999-11-16 17:17 ` Philipp Rumpf
1999-11-16 8:26 ` Philippe Benard
1999-11-16 12:20 ` Alan Cox
1999-11-16 11:53 ` Philippe Benard
1999-11-16 12:58 ` Alan Cox
1999-11-16 15:55 ` John David Anglin
1999-11-17 13:00 ` Philipp Rumpf
1999-11-16 12:35 ` Matthew Wilcox
1999-11-16 16:08 ` Philipp Rumpf
1999-11-16 17:14 ` Alan Cox
1999-11-16 16:47 ` Philipp Rumpf
1999-11-16 17:50 ` Alan Cox
1999-11-17 0:06 ` Grant Grundler
1999-11-17 6:21 ` Philipp Rumpf
1999-11-17 18:57 ` Stan Sieler
1999-11-17 19:29 ` Philipp Rumpf
1999-11-17 20:01 ` Stan Sieler
1999-11-17 20:33 ` Philipp Rumpf
1999-11-16 21:43 ` Frank Rowand
1999-11-17 6:12 ` Philipp Rumpf
1999-11-17 18:56 ` Frank Rowand
1999-11-17 22:05 ` Philipp Rumpf
1999-11-17 22:39 ` John David Anglin
1999-11-17 22:52 ` Philipp Rumpf
1999-11-17 23:37 ` Stan Sieler
1999-11-18 0:09 ` Philipp Rumpf
1999-11-18 0:43 ` Frank Rowand
1999-11-18 1:35 ` Frank Rowand
1999-11-18 5:33 ` John David Anglin
1999-11-18 8:02 ` Philippe Benard
1999-11-18 20:37 ` John David Anglin
1999-11-18 22:38 ` Frank Rowand
1999-11-19 4:12 ` Philipp Rumpf
1999-11-19 9:08 ` Philippe Benard
1999-11-17 23:02 ` Frank Rowand [this message]
1999-11-17 23:25 ` Philipp Rumpf
1999-11-17 8:14 ` Philippe Benard
1999-11-15 8:19 ` Philipp Rumpf
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=3833340E.59C7BDB4@hp.com \
--to=frank_rowand@hp.com \
--cc=frowand@cup.hp.com \
--cc=parisc-linux@thepuffingroup.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