public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: cacheble to uncachble change
Date: Tue, 27 Apr 2004 22:45:48 +0000	[thread overview]
Message-ID: <16526.58012.918419.971565@napali.hpl.hp.com> (raw)
In-Reply-To: <408D5C58.E07A5FBE@email.mot.com>

>>>>> On Tue, 27 Apr 2004 17:35:10 -0500, Mario Smarduch <cms063@email.mot.com> said:

  Mario> I guess the question wasn't so much about attribute aliasing
  Mario> but killing all intransit memory accesses and prefetch before
  Mario> its safe to change the TLB attribute to uncacheble, with
  Mario> assurance that all new mem refs/prefetch will come from
  Mario> memory. I appreciate all your inputs.

Yes, but that's the _easy_ part, so to speak.

To be honest, I would appreciate if you could outline your strategy to
avoid memory-attribute aliasing.  If only because it would give me a
warm-and-fuzzy feeling... ;-)

If this isn't something you're comfortable discussing on a public
list, a private mail would still be appreciated.

Thanks,

	--david

  parent reply	other threads:[~2004-04-27 22:45 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
2004-04-27 22:45 ` David Mosberger [this message]
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=16526.58012.918419.971565@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.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