From: MIke Galbraith <efault@gmx.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Con Kolivas <kernel@kolivas.org>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
gcoady@gmail.com, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6 vs 2.4, ssh terminal slowdown
Date: Wed, 15 Feb 2006 06:22:20 +0100 [thread overview]
Message-ID: <1139980940.24148.47.camel@homer> (raw)
In-Reply-To: <1139977373.2733.9.camel@mindpipe>
On Tue, 2006-02-14 at 23:22 -0500, Lee Revell wrote:
> On Mon, 2006-02-13 at 13:35 +0100, MIke Galbraith wrote:
> > On Mon, 2006-02-13 at 03:43 -0500, Lee Revell wrote:
> > > On Mon, 2006-02-13 at 08:08 +0100, MIke Galbraith wrote:
> > > > On Mon, 2006-02-13 at 01:38 -0500, Lee Revell wrote:
> > > > > Do you know which of those changes fixes the "ls" problem?
> > > >
> > > > No, it could be either, both, or neither. Heck, it _could_ be a
> > > > combination of all of the things in my experimental tree for that
> > > > matter. I put this patch out there because I know they're both bugs,
> > > > and strongly suspect it'll cure the worst of the interactivity related
> > > > delays.
> > > >
> > > > I'm hoping you'll test it and confirm that it fixes yours.
> > >
> > > Nope, this does not fix it. "time ls" ping-pongs back and forth between
> > > ~0.1s and ~0.9s. Must have been something else in the first patch.
> >
> > Hmm. Thinking about it some more, it's probably more than this alone,
> > but it could well be the boost qualifier I'm using...
>
> OK, with 2.6.16-rc2-mm1, "ls" bounces around between 0.15s and 0.50s.
> Better than mainline but the large seemingly random variance is still
> perceptible and annoying. And, "ls | cat" behaves about the same as
> "ls", while on mainline it was consistently faster (!).
Ok. That means the reduction in fluctuation had nothing to do with my
changes. It also suggests that there may be something of a regression
in the changes that are in mm, which I also carried in my patch, since
the timing for both kernels appear to be ~identical with or without my
bits. That seems a little odd to me considering what those changes do.
>
> Do you have an updated patch against -mm that I can test?
I will soon if you still want to try it. I've fixed the throttle release
thing, and am fine tuning the interactivity bits. I have it working
very well now, but want to try to squeeze some more from it.
Drop me a line if you're still interested from the interactivity side,
but I think the ls delay reduction has turned out to be a red herring.
-Mike
next prev parent reply other threads:[~2006-02-15 5:22 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
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 [this message]
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=1139980940.24148.47.camel@homer \
--to=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 \
--cc=rlrevell@joe-job.com \
/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