From: Mario Smarduch <cms063@email.mot.com>
To: linux-ia64@vger.kernel.org
Subject: Re: cacheble to uncachble change
Date: Tue, 27 Apr 2004 22:35:10 +0000 [thread overview]
Message-ID: <408EE01E.42630BD8@email.mot.com> (raw)
In-Reply-To: <408D5C58.E07A5FBE@email.mot.com>
David Mosberger wrote:
> >>>>> On Tue, 27 Apr 2004 16:31:57 -0500, Jack Steiner <steiner@sgi.com> said:
>
> Jack> Maybe I was not clear. I *know* that memory attribute aliasing
> Jack> is a bad thing to do. I was commenting on Robin's mail and
> Jack> providing a real-life example on where/how it causes
> Jack> problems. Prefetching is a perfectly valid thing for the cpu
> Jack> to do. Any time there is a valid TLB entry, prefetching can &
> Jack> will happen. DONT allow a TLB entry to cover both cached &
> Jack> uncached pages.
>
> Sounds like we're in violent agreement! ;-)
>
> --david
I guess the question wasn't so much about attribute aliasing but
killing all intransit memory accesses and prefetch before its
safe to change the TLB attribute to uncacheble, with assurance that
all new mem refs/prefetch will come from memory. I appreciate
all your inputs.
- Mario.
next prev parent reply other threads:[~2004-04-27 22:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-26 18:57 cacheble to uncachble change Mario Smarduch
2004-04-26 19:25 ` David Mosberger
2004-04-26 21:24 ` Jim Hull
2004-04-26 21:35 ` Robin Holt
2004-04-26 21:46 ` David Mosberger
2004-04-27 0:03 ` David Mosberger
2004-04-27 10:52 ` Robin Holt
2004-04-27 14:24 ` Jack Steiner
2004-04-27 19:50 ` David Mosberger
2004-04-27 21:31 ` Jack Steiner
2004-04-27 21:48 ` David Mosberger
2004-04-27 22:35 ` Mario Smarduch [this message]
2004-04-27 22:45 ` David Mosberger
2004-04-27 23:53 ` Luck, Tony
2004-04-28 1:43 ` Robin Holt
2004-04-28 15:52 ` Mario Smarduch
2004-04-29 4:49 ` David Mosberger
2004-04-29 13:39 ` Smarduch Mario-CMS063
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=408EE01E.42630BD8@email.mot.com \
--to=cms063@email.mot.com \
--cc=linux-ia64@vger.kernel.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