All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: tty update speed regression (was: 2.6.14-rc2-mm1)
Date: Thu, 22 Sep 2005 17:08:15 -0700	[thread overview]
Message-ID: <20050923000815.GB2973@us.ibm.com> (raw)
In-Reply-To: <20050922214926.GA6524@mipter.zuzino.mipt.ru>

On 23.09.2005 [01:49:26 +0400], Alexey Dobriyan wrote:
> On Thu, Sep 22, 2005 at 11:50:29PM +0400, Alexey Dobriyan wrote:
> > I see regression in tty update speed with ADOM (ncurses based
> > roguelike) [1].
> > 
> > Messages at the top ("goblin hits you") are printed slowly. An eye can
> > notice letter after letter printing.
> > 
> > 2.6.14-rc2 is OK.
> > 
> > I'll try to revert tty-layer-buffering-revamp*.patch pieces and see if
> > it'll change something.
> > 
> > [1] http://adom.de/adom/download/linux/adom-111-elf.tar.gz (binary only)
> 
> Scratch TTY revamp, the sucker is
> fix-sys_poll-large-timeout-handling.patch
> 
> HZ=250 here.

Alexey,

Thanks for the report. I will take a look on my Thinkpad with HZ=250
under -mm2. I have some ideas for debugging it if I see the same
problem.

Thanks,
Nish

  reply	other threads:[~2005-09-23  0:08 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22  5:28 2.6.14-rc2-mm1 Andrew Morton
2005-09-22  6:35 ` 2.6.14-rc2-mm1 Joel Becker
2005-09-22  6:46 ` 2.6.14-rc2-mm1 Reuben Farrelly
2005-09-22  7:03   ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-22 18:59 ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-22 19:52   ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-22 20:14     ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-23  0:28       ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-22 22:28     ` 2.6.14-rc2-mm1 - ide problems ? Badari Pulavarty
2005-09-22 23:39       ` Andrew Morton
2005-09-22 19:50 ` tty update speed regression (was: 2.6.14-rc2-mm1) Alexey Dobriyan
2005-09-22 21:49   ` Alexey Dobriyan
2005-09-23  0:08     ` Nishanth Aravamudan [this message]
2005-09-23 17:12       ` Nish Aravamudan
2005-09-23 18:42         ` Alexey Dobriyan
2005-09-23 19:07           ` Nishanth Aravamudan
2005-09-23 19:42             ` Alexey Dobriyan
2005-09-23 21:32               ` Nishanth Aravamudan
2005-09-24 17:43 ` 2.6.14-rc2-mm1 Mattia Dongili
2005-09-24 17:58 ` 2.6.14-rc2-mm1 Mattia Dongili
2005-09-24 18:23   ` 2.6.14-rc2-mm1 Andrew Morton
2005-09-26 19:33     ` 2.6.14-rc2-mm1 Seth, Rohit
2005-09-27 18:57       ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 20:05         ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 21:18           ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 21:51             ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 21:59               ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 22:49                 ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27 22:49                   ` 2.6.14-rc2-mm1 Martin J. Bligh
2005-09-27 23:16                     ` 2.6.14-rc2-mm1 Rohit Seth
2005-09-27  7:13 ` 2.6.14-rc2-mm1 (Oops, possibly Netfilter related?) Reuben Farrelly
2005-09-27  7:44   ` Andrew Morton
2005-09-27 18:59     ` Martin J. Bligh
2005-10-02 17:13       ` Paul Jackson
2005-10-02 21:31         ` Martin J. Bligh
2005-10-03 17:20           ` Rohit Seth
2005-10-03 17:56             ` Martin J. Bligh

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=20050923000815.GB2973@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.