From: Mike Galbraith <efault@gmx.de>
To: rwhron@earthlink.net, ingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: Re: scheduler starvation running irman with 2.5.64bk2
Date: Tue, 11 Mar 2003 03:37:57 +0100 [thread overview]
Message-ID: <5.2.0.9.2.20030311033325.00c854c8@pop.gmx.net> (raw)
In-Reply-To: <20030311000923.GA1315@rushmore>
At 07:09 PM 3/10/2003 -0500, rwhron@earthlink.net wrote:
> > OK, can you do the following to determine whether we're both seeing the
> > _same_ problem?
>
> > 1.) build the attached rtnice utility (don't remember who wrote/posted
> this)
> > 2.) login on vt1 and set the shell SCHED_RR via rtnice -n 1 -p <pid_of_sh>
> > -d RR
> > 3.) login on vt2 and renice that shell to -10
> > 4.) login on another vt as a normal user, and start irman
> > 5.) try login/out on another vt, or ps or _whatever_ (doesn't matter)
> > until box is starving
> > 6.) on vt2, try to do ps (it should hang despite -10 priority)
> > 7.) on vt1, try to do ps (it should work just fine)
>
>Here is the test as I understand it, splitted by tty. Quick summary,
>only new process seems starved. RR and nice -10 process behave okay.
>
>BTW, this is now with 2.5.64bk5.
The only difference I see is that reniced task wasn't starved with this
kernel... wonder what the difference is. Thanks for running the test.
-Mike
next prev parent reply other threads:[~2003-03-11 2:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 0:09 rwhron
2003-03-11 2:37 ` Mike Galbraith [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-11 2:46 rwhron
2003-03-11 3:43 ` Mike Galbraith
2003-03-09 2:50 rwhron
2003-03-09 3:07 ` Zwane Mwaikambo
2003-03-09 18:59 ` Mike Galbraith
2003-03-09 19:13 ` Mike Galbraith
2003-03-10 4:42 ` Mike Galbraith
2003-03-10 4:46 ` Mike Galbraith
2003-03-10 5:54 ` Mike Galbraith
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=5.2.0.9.2.20030311033325.00c854c8@pop.gmx.net \
--to=efault@gmx.de \
--cc=ingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=rwhron@earthlink.net \
/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
all inboxes | Powered by JetHome®