From: Robert Love <rml@ufl.edu>
To: Roger Larsson <roger.larsson@norran.net>
Cc: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: Re: Feedback on preemptible kernel patch
Date: 18 Sep 2001 19:31:28 -0400 [thread overview]
Message-ID: <1000855890.19833.51.camel@phantasy> (raw)
In-Reply-To: <200109181822.f8IIMv618968@mailg.telia.com>
In-Reply-To: <200109140302.f8E32LG13400@zero.tech9.net> <1000530869.32365.21.camel@phantasy> <20010918040550Z273827-761+10122@vger.kernel.org> <200109181822.f8IIMv618968@mailg.telia.com>
On Tue, 2001-09-18 at 14:18, Roger Larsson wrote:
> Do you run with the playback process reniced -N?
> It should really run with a low SCHED_FIFO or SCHED_RT policy.
> But renicing it with a negative value gives some of the benefits...
> (but you need to run as root)
> In addition to this the program might need to lock its pages down - the
> only thing I can think of that could cause several seconds delay would
> be if it has been swapped out...
Certainly giving it a higher priority should improve results (especially
with preemption), but the application should receive a fair amount of
process attention as it is, as it is TASK_RUNNABLE at all times and the
disk I/O should be routinely preempted. I am interested how much
renicing it helps, though.
Now, if it has to swap pages, that is a very good point. I tend to
blame this, or perhaps something with a long held lock (the audio
driver?) for the blips.
Its so hard to tell swap/VM issues now with all the VM work, sadly...:)
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-09-18 23:30 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200109150444.f8F4iEG19063@zero.tech9.net>
[not found] ` <200109140302.f8E32LG13400@zero.tech9.net>
2001-09-14 4:35 ` Feedback on preemptible kernel patch Robert Love
2001-09-15 4:25 ` Dieter Nützel
2001-09-15 5:14 ` Robert Love
2001-09-18 4:06 ` Dieter Nützel
2001-09-18 8:35 ` Daniel Phillips
2001-09-18 18:18 ` Roger Larsson
2001-09-18 23:31 ` Robert Love [this message]
2001-09-20 6:40 ` Dieter Nützel
2001-09-18 23:31 ` Robert Love
2001-09-15 19:18 Robert Love
2001-09-16 1:28 ` Daniel Phillips
2001-09-16 1:54 ` Daniel Phillips
[not found] <Pine.LNX.4.33.0109140838040.21992-100000@sjoerd.sjoerdnet>
2001-09-14 15:04 ` Robert Love
2001-09-15 9:44 ` Arjan Filius
2001-09-15 10:38 ` Erik Mouw
2001-09-15 17:57 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-09-14 2:47 Dieter Nützel
2001-09-11 22:53 Robert Love
2001-09-08 5:22 grue
2001-09-08 5:47 ` Robert Love
2001-09-08 17:33 ` Arjan Filius
2001-09-08 18:22 ` safemode
2001-09-09 4:40 ` Robert Love
2001-09-09 17:09 ` Robert Love
2001-09-09 21:07 ` Arjan Filius
2001-09-09 21:26 ` Robert Love
2001-09-09 21:23 ` Arjan Filius
2001-09-09 21:37 ` Robert Love
2001-09-10 3:24 ` Daniel Phillips
2001-09-10 3:37 ` Jeremy Zawodny
2001-09-10 5:09 ` Robert Love
2001-09-10 18:25 ` Daniel Phillips
2001-09-10 21:29 ` Arjan Filius
2001-09-13 17:27 ` Robert Love
2001-09-14 7:30 ` george anzinger
2001-09-14 15:01 ` Robert Love
2001-09-11 19:47 ` Arjan Filius
2001-09-09 18:57 ` grue
2001-09-09 21:44 ` Robert Love
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=1000855890.19833.51.camel@phantasy \
--to=rml@ufl.edu \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.larsson@norran.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;
as well as URLs for NNTP newsgroup(s).