From: Grant Grundler <grundler@cup.hp.com>
To: "Van Maren, Kevin" <kevin.vanmaren@unisys.com>
Cc: "'Mario Smarduch '" <cms063@email.mot.com>,
"'davidm+AEA-hpl.hp.com '" <davidm@hpl.hp.com>,
"'Mario Smarduch '" <CMS063@motorola.com>,
"'linux-ia64+AEA-linuxia64.org '" <linux-ia64@linuxia64.org>,
"'linux-kernel+AEA-vger.kernel.org '"
<linux-kernel@vger.kernel.org>,
grundler@cup.hp.com
Subject: Re: [Linux-ia64] RE: +AFs-Linux-ia64+AF0- reader-writer livelock proble
Date: Mon, 11 Nov 2002 14:02:32 -0800 [thread overview]
Message-ID: <20021111220232.C94F712C0C@debian.cup.hp.com> (raw)
In-Reply-To: Your message of "Mon, 11 Nov 2002 14:36:38 CST." <3FAD1088D4556046AEC48D80B47B478C0101F4F7@usslc-exch-4.slc.unisys.com>
"Van Maren, Kevin" wrote:
> It is also possible that a processor can get stuck +ACI-forever+ACI-
> spinning in the kernel with interrupts disabled trying to
> acquire a lock, and never succeed, without the rest of the
> kernel going south. If that happens, and application will
> be livelocked, but the rest of the system will function.
Probably not. ia64 systems (and x86 systems with IO xapic) direct
IO interrupts to specific CPUs. Devices would not get serviced
in the above case and IO to/from those devices would come to a
grinding halt. It would look more like "dead" lock than "live" lock.
> It really depends on the particular circumstances.
yes. But it sounds very likely to me.
grant
prev parent reply other threads:[~2002-11-11 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3FAD1088D4556046AEC48D80B47B478C0101F4F7@usslc-exch-4.slc.unisys.com>
2002-11-11 21:21 ` +AFs-Linux-ia64+AF0- reader-writer livelock proble David Mosberger
2002-11-11 22:02 ` Grant Grundler [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=20021111220232.C94F712C0C@debian.cup.hp.com \
--to=grundler@cup.hp.com \
--cc=CMS063@motorola.com \
--cc=cms063@email.mot.com \
--cc=davidm@hpl.hp.com \
--cc=kevin.vanmaren@unisys.com \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).