All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: O(1) MQ scheduler J9 patch for IA64
Date: Fri, 08 Feb 2002 06:11:28 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698806025@msgid-missing> (raw)

  Erich> I had to add a function smp_call_function_nowait which sends
  Erich> an IPI and returns immediately in order to get rid of a
  Erich> IA64-specific race condition when the mmu_context wraps
  Erich> around. Now it makes a very stable and fast impression,
  Erich> interactive work is even possible while doing a "hackbench
  Erich> 55" and ping flooding the machine... Tested on 2 CPU BigSur,
  Erich> 4 CPU LION, 16 CPU AzusA.

Hmmh, I'm a bit worried that this is a fragile solution.  It would
break if there ever was a scenario where a task migrated from one CPU
to another while the target CPU has interrupts disabled.  I do not
think this can happen with Ingo's current scheduler but I'd prefer a
more robust solution.

A somewhat cheesy solution might be to have a per-CPU flag that
indicates whether a CPU should flush its TLB before switching to the
next task.  We could check for this in activate_mm().  Do you want to
try this?

	--david


             reply	other threads:[~2002-02-08  6:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08  6:11 David Mosberger [this message]
2002-02-08  6:37 ` [Linux-ia64] Re: O(1) MQ scheduler J9 patch for IA64 William Lee Irwin III
2002-02-08  6:40 ` David Mosberger
2002-02-08 17:37 ` [Linux-ia64] Re: O(1) MQ scheduler J9 patch for IA64 -> K3 patch Erich Focht

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-105590698806025@msgid-missing \
    --to=davidm@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.