public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [2.6.16-rc6 patch] fix interactive task starvation
Date: Sat, 18 Mar 2006 10:43:56 +0100	[thread overview]
Message-ID: <1142675036.9000.3.camel@homer> (raw)
In-Reply-To: <200603181915.48098.kernel@kolivas.org>

On Sat, 2006-03-18 at 19:15 +1100, Con Kolivas wrote:
> On Saturday 18 March 2006 19:05, Andrew Morton wrote:
> > Mike Galbraith <efault@gmx.de> wrote:
> > > The patch below fixes a starvation problem that occurs when a stream of
> > >  highly interactive tasks delay an array switch for extended periods
> > >  despite EXPIRED_STARVING(rq) being true.  AFAIKT, the only choice is to
> > >  enqueue awakening tasks on the expired array in this case.
> > >
> > >  Without this patch, it can be nearly impossible to remotely login to a
> > >  busy server, and interactive shell commands can starve for minutes.
> > >
> > >  This has not been verified by anyone.  Comments?
> >
> > What does that question mean, btw?
> 
> He's waiting for me to say I don't like it. But I do like it.

<chuckle>

No.  Actually, I'm waiting for Ingo to just yawn and nuke the problem
with a casual flick of his pinkie.

	-Mike


  reply	other threads:[~2006-03-18  9:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18  5:08 [2.6.16-rc6 patch] fix interactive task starvation Mike Galbraith
2006-03-18  5:15 ` Andrew Morton
2006-03-18  5:50   ` Mike Galbraith
2006-03-18  6:22     ` Andrew Morton
2006-03-18  7:29       ` Mike Galbraith
2006-03-18  7:33         ` Andrew Morton
2006-03-18  7:48           ` Mike Galbraith
2006-03-18  7:52             ` Andrew Morton
2006-03-18  8:51         ` Ingo Molnar
2006-03-18  8:05 ` Andrew Morton
2006-03-18  8:15   ` Con Kolivas
2006-03-18  9:43     ` Mike Galbraith [this message]
2006-03-18  8:52   ` Ingo Molnar

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=1142675036.9000.3.camel@homer \
    --to=efault@gmx.de \
    --cc=akpm@osdl.org \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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