From: David Mosberger <davidm@napali.hpl.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>
Subject: RE: +AFs-Linux-ia64+AF0- reader-writer livelock proble
Date: Mon, 11 Nov 2002 13:21:34 -0800 [thread overview]
Message-ID: <15824.8030.745186.6665@napali.hpl.hp.com> (raw)
In-Reply-To: <3FAD1088D4556046AEC48D80B47B478C0101F4F7@usslc-exch-4.slc.unisys.com>
>>>>> On Mon, 11 Nov 2002 14:36:38 -0600, "Van Maren, Kevin" <kevin.vanmaren@unisys.com> said:
Van> I have not looked at this, but I don't believe it is the right
Van> way to solve the problem: users who +AF8-need+AF8- to use all
Van> the CPUs for computation would be punished just to work around
Van> a kernel implementation issue: that's like saying don't allow
Van> processes to allocate virtual memory because if the VM is
Van> over-committed by X amount the kernel deadlocks.
Van> It would be a bad hack to limit the system-call rate just to
Van> prevent livelock.
Certainly. I didn't suggest PRM as a way to _solve_ the livelock
problem, but since Mario asked for a method to cap CPU utilization, I
mentiond it.
--david
next parent reply other threads:[~2002-11-11 21:16 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 ` David Mosberger [this message]
2002-11-11 22:02 ` [Linux-ia64] RE: +AFs-Linux-ia64+AF0- reader-writer livelock proble Grant Grundler
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=15824.8030.745186.6665@napali.hpl.hp.com \
--to=davidm@napali.hpl.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).