From: Willy Tarreau <willy@w.ods.org>
To: Grant Coady <gcoady@gmail.com>
Cc: Con Kolivas <kernel@kolivas.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6 vs 2.4, ssh terminal slowdown
Date: Wed, 8 Feb 2006 06:17:09 +0100 [thread overview]
Message-ID: <20060208051709.GE11380@w.ods.org> (raw)
In-Reply-To: <nutiu1dkoldca31ddusfbd2rv41q7q0k3m@4ax.com>
Hi Grant,
On Wed, Feb 08, 2006 at 03:51:24PM +1100, Grant Coady wrote:
> On Wed, 8 Feb 2006 14:00:59 +1100, Con Kolivas <kernel@kolivas.org> wrote:
>
> >This is the terminal's fault. xterm et al use an algorithm to determine how
> >fast your machine is and decide whether to jump scroll or smooth scroll. This
> >algorithm is basically broken with the 2.6 scheduler and it decides to mostly
> >smooth scroll.
>
> Strange it does that over localnet to a PuTTY terminal on windoze.
>
> Seems a strange thing to do in the kernel though, presentation
> buffering / management surely can be done in userspace?
I suspect the sshd on the firewall gets woken up for each line and it
behaves exactly like an xterm. After having done a lot of "ls -l|cat"
on 2.6, I'm not surprized at all :-/
A good test would be to strace sshd under 2.4 and 2.6. You could even
use strace -tt. Probably that you will see something like 1 ms between
two reads on 2.6 and nearly nothing between them in 2.4.
> Grant.
Cheers,
Willy
next prev parent reply other threads:[~2006-02-08 5:17 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 [this message]
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
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=20060208051709.GE11380@w.ods.org \
--to=willy@w.ods.org \
--cc=gcoady@gmail.com \
--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