All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: TLB flushing on SGI platforms
Date: Mon, 01 Dec 2003 21:42:06 +0000	[thread overview]
Message-ID: <marc-linux-ia64-107031512728461@msgid-missing> (raw)

>>>>> On Wed, 26 Nov 2003 09:43:01 -0600, Jack Steiner <steiner@sgi.com> said:

  Jack> The SGI NUMA platform does not use the hardware "ptc" instruction
  Jack> to flush TLBs. Instead, it has to write an MMR on the chipset on each
  Jack> node to cause a TLB flush transaction to be placed on the bus. On
  Jack> large systems, the overhead to broadcast the TLB flush to every node
  Jack> in the system is one of the hot spots in the kernel.

  Jack> In most cases, the TLB context being flushed has been loaded into
  Jack> a small subset of the nodes. Flushing every node is unnecessary.

  Jack> I'm looking for suggestions on the best way to limit TLB flushing so
  Jack> that only the necessary nodes are flushed. Here is patch that
  Jack> I believe will work. I added a bitmask to the mm_context_t to
  Jack> track nodes where the context has been loaded. The TLB flush routine
  Jack> issues the TLB flush requests only to these nodes.

  Jack> Are there other/better ways that I can do this??

Why not use mm->cpu_vm_mask?  It will give you CPU instead of
node-granularity, but if you really want nodes instead, you can do the
mapping in the NUMA-specific code.

	--david

             reply	other threads:[~2003-12-01 21:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 21:42 David Mosberger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-26 15:43 TLB flushing on SGI platforms Jack Steiner

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=marc-linux-ia64-107031512728461@msgid-missing \
    --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 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.