From: Lee Revell <rlrevell@joe-job.com>
To: MIke Galbraith <efault@gmx.de>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Con Kolivas <kernel@kolivas.org>,
gcoady@gmail.com, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6 vs 2.4, ssh terminal slowdown
Date: Sun, 12 Feb 2006 22:39:34 -0500 [thread overview]
Message-ID: <1139801975.2739.72.camel@mindpipe> (raw)
In-Reply-To: <1139800169.7595.24.camel@homer>
On Mon, 2006-02-13 at 04:09 +0100, MIke Galbraith wrote:
> On Sun, 2006-02-12 at 18:39 -0500, Lee Revell wrote:
> > On Sun, 2006-02-12 at 22:36 +0100, MIke Galbraith wrote:
> > > On Sun, 2006-02-12 at 14:03 -0500, Lee Revell wrote:
> > > > On Sun, 2006-02-12 at 14:47 +0100, MIke Galbraith wrote:
> > > > > If you think it's the scheduler, how about try the patch below. It's
> > > > > against 2.6.16-rc2-mm1, and should tell you if it is the interactivity
> > > > > logic in the scheduler or not. I don't see other candidates in there,
> > > > > not that that means there aren't any of course.
> > > >
> > > > I'll try, but it's a serious pain for me to build an -mm kernel. A
> > > > patch against 2.6.16-rc1 would be much easier.
> > >
> > > Ok, here she comes. It's a bit too reluctant to release a task so it
> > > can reach interactive status at the moment, but for this test, that's a
> > > feature. In fact, for this test, it's probably best to jump straight to
> > > setting both g1 and g2 to zero.
> >
> > Not only does this fix my "time ls" test case, it seems to drastically
> > improve interactivity for my desktop apps. I was really being plagued
> > by weird stalls, it's much smoother now.
>
> Yeah, but under load, that reluctance to release is fairly annoying...
This seems to manifest on my system as the mouse getting jerky under
load. Still, I don't mind - the overall feel is still smoother - as if
the X server was getting too much CPU before.
Lee
next prev parent reply other threads:[~2006-02-13 3:39 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 2:11 2.6 vs 2.4, ssh terminal slowdown Grant Coady
2006-02-08 2:24 ` Benjamin LaHaise
2006-02-08 2:50 ` Grant Coady
2006-02-08 3:02 ` Benjamin LaHaise
2006-02-08 2:35 ` Con Kolivas
2006-02-08 2:55 ` Grant Coady
2006-02-08 3:00 ` Con Kolivas
2006-02-08 4:12 ` Barry K. Nathan
2006-02-08 4:41 ` Grant Coady
2006-02-08 4:51 ` Grant Coady
2006-02-08 5:17 ` Willy Tarreau
2006-02-08 5:39 ` Grant Coady
2006-02-08 7:43 ` Lee Revell
2006-02-09 17:06 ` Jan Engelhardt
2006-02-09 20:06 ` Lee Revell
2006-02-10 6:35 ` MIke Galbraith
2006-02-12 13:47 ` MIke Galbraith
2006-02-12 19:03 ` Lee Revell
2006-02-12 21:36 ` MIke Galbraith
2006-02-12 23:23 ` Lee Revell
2006-02-12 23:39 ` Lee Revell
2006-02-13 3:09 ` MIke Galbraith
2006-02-13 3:39 ` Lee Revell [this message]
2006-02-13 4:59 ` MIke Galbraith
2006-02-13 5:05 ` Con Kolivas
2006-02-13 5:32 ` MIke Galbraith
2006-02-13 5:37 ` Con Kolivas
2006-02-13 5:57 ` MIke Galbraith
2006-02-13 6:08 ` Con Kolivas
2006-02-13 6:35 ` MIke Galbraith
2006-02-13 6:38 ` Lee Revell
2006-02-13 7:08 ` MIke Galbraith
2006-02-13 8:43 ` Lee Revell
2006-02-13 10:06 ` MIke Galbraith
2006-02-13 12:35 ` MIke Galbraith
2006-02-15 4:22 ` Lee Revell
2006-02-15 5:22 ` MIke Galbraith
2006-02-15 6:11 ` Lee Revell
2006-02-15 7:17 ` MIke Galbraith
2006-02-13 7:15 ` Con Kolivas
2006-02-13 7:41 ` 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=1139801975.2739.72.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=efault@gmx.de \
--cc=gcoady@gmail.com \
--cc=jengelh@linux01.gwdg.de \
--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