public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Linux-ia64] 2.4.5 hangs in smp_call_function.
Date: Fri, 08 Jun 2001 20:03:38 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005703@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005699@msgid-missing>

Actually, I'd like to remove support for anything older than B3 in the
not too distant future.  I can leave the code there for a while
longer, but I'm considering it unsupported.  Also, note that this
means that if you find a bug that shows up only on pre-B3 systems, I
don't care about it and don't want to hear about it... ;-)

	--david

>>>>> On Fri, 8 Jun 2001 11:49:55 -0700, "Seth, Rohit" <rohit.seth@intel.com> said:

  Rohit> Jack, The only change that is needed is to change the value
  Rohit> of timeout from HZ to 400...  The race condition where source
  Rohit> processor is getting out of while (timeout) loop and target
  Rohit> processor is just about to send the acknowledgement (by
  Rohit> setting the started field) will most likely not happen for
  Rohit> such a big timeout. And as this code is only for earlier
  Rohit> stepping so it should be okay.  Though I think that HZ itself
  Rohit> is big enough but then seems like your system is under severe
  Rohit> load and taking longer to respond for IPIs.

  Rohit> Besides that the other changes are not needed.  In fact there
  Rohit> are couple of things that you should not do 1: don't include
  Rohit> resend_list_IPI even when CONFIG_ITANIUM_PTCG is defined 2:
  Rohit> don't just continue to be in while loop without resending the
  Rohit> IPI again for the cases when you really have a lost IPI.


  parent reply	other threads:[~2001-06-08 20:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07 22:00 [Linux-ia64] 2.4.5 hangs in smp_call_function Jack Steiner
2001-06-08 18:49 ` Seth, Rohit
2001-06-08 20:03 ` David Mosberger [this message]
2001-06-12  6:37 ` root

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-105590693005703@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox