From: Bill Huey (hui) <billh@gnuppy.monkey.org>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux Kernel M/L <linux-kernel@vger.kernel.org>,
Con Kolivas <kernel@kolivas.org>, Ingo Molnar <mingo@elte.hu>,
"Bill Huey (hui)" <billh@gnuppy.monkey.org>
Subject: Re: [REPORT] 2.6.21 vs. 2.6.21-sd046 vs. 2.6.21-CFSv7
Date: Mon, 30 Apr 2007 13:16:59 -0700 [thread overview]
Message-ID: <20070430201659.GA5681@gnuppy.monkey.org> (raw)
In-Reply-To: <46364A75.9080003@tmr.com>
On Mon, Apr 30, 2007 at 03:58:45PM -0400, Bill Davidsen wrote:
> Followup: I reran with sd-0.46, setting rr_interval to 40, and then 5
> (default was 16). Neither appeared to give a useful video playback. I
> did try setting the make to nice 10, and that made the playback
> perfectly smooth, as well as response to skip forward and volume change
> happening when the key was pressed instead of eventually.
>
> I also tried raising the nice of X to -10, that made things better on
> display, but I winder if it will let X run ahead of the nice-0 raid threads.
>
> Is this my hardware or is there a really odd behavior here? The sd seems
> to be too fair to cope well with this realistic load, and expecting
> users to nice things is probably morally correct but unrealistic.
People have been reporting very good performance with regards to OpenGL
applications under SD. What is your video driver ? NVidia proprietary ?
OpenGL, X and direct frame buffer access (mplayer and friends) tend not
to interact each other which can result in very different scheduling
characteristics between them.
[please CC the relevant people for their own benefit]
bill
next prev parent reply other threads:[~2007-04-30 20:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 19:29 [REPORT] 2.6.21 vs. 2.6.21-sd046 vs. 2.6.21-CFSv7 Bill Davidsen
2007-04-30 19:58 ` Bill Davidsen
2007-04-30 20:16 ` Bill Huey [this message]
2007-05-02 15:11 ` Bill Davidsen
2007-04-30 22:51 ` Con Kolivas
2007-05-02 15:18 ` Bill Davidsen
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=20070430201659.GA5681@gnuppy.monkey.org \
--to=billh@gnuppy.monkey.org \
--cc=davidsen@tmr.com \
--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