From: Mike Galbraith <efault@gmx.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] patch-O1int-0306302317 for 2.5.73 interactivity
Date: Tue, 01 Jul 2003 18:31:11 +0200 [thread overview]
Message-ID: <5.2.0.9.2.20030701174513.026efe70@pop.gmx.net> (raw)
In-Reply-To: <200307012329.49069.kernel@kolivas.org>
At 11:29 PM 7/1/2003 +1000, Con Kolivas wrote:
>On Tue, 1 Jul 2003 23:17, Felipe Alfaro Solana wrote:
> > On Tue, 2003-07-01 at 14:04, Con Kolivas wrote:
> > > >When I say "X feels jerky", I mean that I can notice the scheduler is
> > > >not giving the X server enough CPU cycles (I mean, a continuous,
> > > >smaller, but more frequent CPU timeslice) to perform window movement and
> > > >redrawing fast enough to get ~25fps. Also, I don't think it's related to
> > > >the video card. The combo patch I did with Mike's + Ingo's enhacements
> > > >works beautifully for me.
> > >
> > > Actually just the bastardised Ingo patch will do that on it's own.
> > > However that's never going to be incorporated.
> >
> > So, I guess we won't have the option to choose between different CPU
> > schedulers (desktop or server, for example), like we have in -mm kernels
> > with IO schedulers (deadline or anticipatory).
> >
> > Seriously talking, I prefer to have the best performance in my server
> > boxes, but for my laptop, I prefer shorter timeslices, lower peformance
> > and better turnaround times and a wiser CPU scheduler. Just my two
> > cents.
> >
> > It's sad to say but I feel the vanilla 2.5 CPU scheduler doesn't match
> > my end-user preferences :-(
>
>There will always be alternate trees. Whether options like this make it into
>mainline will be up to the maintainer of course, but given that we seem to
>have a "swappiness" dial in mainline then I suspect we may have more dials in
>2.6 than before.
I don't like knobs at all [1], but I have to ~agree with Felipe.
A prime candidate for a knob (rather switch) would be a slightly more sane
back-boost for desktop use. I'm playing with back-boost in my tree,
allowing a limited quantity, and strictly from user tasks... it helps the
desktop quite a bit. Another thing that's very important for the desktop
(and shell) is startup time for new tasks. I'm working on something there
too (works great when it's not busy breaking everything to
pieces;). Modulo me ever getting that darn thing working acceptably well,
another candidate is to either export CHILD_PENALTY as in scheduler knobs
patch, or just set it to ~75-~85 when back-boost is enabled, ie make one
desktop mode switch and hope like heck it doesn't cause more trouble than
it's worth.
-Mike
1. Dear LKML, why does performance suck? My .config and 10000 random knob
settings attached.
next prev parent reply other threads:[~2003-07-01 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 14:29 Con Kolivas
2003-06-30 18:27 ` Zwane Mwaikambo
2003-06-30 22:50 ` Con Kolivas
2003-06-30 21:21 ` Felipe Alfaro Solana
2003-06-30 21:54 ` Con Kolivas
2003-07-01 8:59 ` Felipe Alfaro Solana
2003-07-01 9:31 ` Con Kolivas
2003-07-01 12:00 ` Felipe Alfaro Solana
2003-07-01 12:04 ` Con Kolivas
2003-07-01 13:17 ` Felipe Alfaro Solana
2003-07-01 13:29 ` Con Kolivas
2003-07-01 16:31 ` Mike Galbraith [this message]
2003-06-30 22:03 ` Wiktor Wodecki
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.20030701174513.026efe70@pop.gmx.net \
--to=efault@gmx.de \
--cc=felipe_alfaro@linuxmail.org \
--cc=kernel@kolivas.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
all inboxes | Powered by JetHome®