From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Global Purge Translation Cache on NUM systems
Date: Fri, 26 Aug 2005 00:38:41 +0000 [thread overview]
Message-ID: <7735.1125016721@ocs3.ocs.com.au> (raw)
In-Reply-To: <A752C16E6296D711942200065BFCB69424BFFF47@il02exm10>
On Thu, 25 Aug 2005 13:15:33 -0500,
Smarduch Mario-CMS063 <CMS063@motorola.com> wrote:
>
>We've been noticing some TLB issues on 2.4 and 2.6.10 kernels running
>on IA64 NUMA architecture. To this end I have some questions regarding
>TLB purging, please bare through with the initial introduction.
>
>IA64 Inst Set Manual points out that propogation of ptc.g across local
>cache coherence domains is platform dependent and must be handled by
>software. I'm trying to understand how would this work on a ccNUMA and
>whether or not software beyond what hw offers to propgate a ptc.ga
>(Purte TC bus transaction) is needed.
See platform_global_tlb_purge. On ccNUMA boxes it gets defined to a
platform specific routine. On SGI's SN2, platform_global_tlb_purge
ends up calling sn2_global_tlb_purge(). That routine works out if the
flush is for the current cpu, for a cpu on the same node or for a
remote node and handles the flush accordingly.
>When a Purge TC global is issued is hardware responsible for keeping the xaction from completion (TND#
>assertion) until the xaction has become visible to all nodes?
The platform's tlb purge routine is responsible for synchronization.
It must not return to the caller of platform_global_tlb_purge() until
the tlb has been flushed on all the target nodes. IOW, software make
non-sync hardware look synchronous.
prev parent reply other threads:[~2005-08-26 0:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 18:15 Global Purge Translation Cache on NUM systems Smarduch Mario-CMS063
2005-08-26 0:38 ` Keith Owens [this message]
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=7735.1125016721@ocs3.ocs.com.au \
--to=kaos@sgi.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