From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mike Galbraith <efault@gmx.de>, Robert Swan <swan.r.l@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [bisected] pty performance problem
Date: Mon, 23 Nov 2009 12:48:45 +0100 [thread overview]
Message-ID: <20091123114845.GC25575@elte.hu> (raw)
In-Reply-To: <20091123113110.15063a0a@lxorguk.ukuu.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > diff --git a/drivers/char/tty_buffer.c b/drivers/char/tty_buffer.c
> > index 66fa4e1..92a0864 100644
> > --- a/drivers/char/tty_buffer.c
> > +++ b/drivers/char/tty_buffer.c
> > @@ -495,7 +495,7 @@ void tty_flip_buffer_push(struct tty_struct *tty)
> > if (tty->low_latency)
> > flush_to_ldisc(&tty->buf.work.work);
> > else
> > - schedule_delayed_work(&tty->buf.work, 1);
> > + schedule_delayed_work(&tty->buf.work, 0);
> > }
> > EXPORT_SYMBOL(tty_flip_buffer_push);
>
> Another possibility is to do
>
> if (tty->low_latency)
> schedule_delayed_work(&tty->buf.work, 0);
> else
> schedule_delayed_work(&tty->buf.work, 1);
Flaggery for low latency is kind of lame though - especially if it
defaults to off in most drivers as you say.
Ingo
next prev parent reply other threads:[~2009-11-23 11:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-21 22:23 [bisected] pty performance problem Robert Swan
2009-11-21 23:23 ` Alan Cox
2009-11-22 0:27 ` Robert Swan
2009-11-22 12:29 ` Alan Cox
2009-11-22 12:41 ` Mike Galbraith
2009-11-22 21:37 ` Robert Swan
2009-11-22 6:39 ` Ingo Molnar
2009-11-22 7:15 ` Arjan van de Ven
2009-11-22 21:56 ` Robert Swan
2009-11-22 12:23 ` Alan Cox
2009-11-22 12:42 ` Ingo Molnar
2009-11-23 5:00 ` Mike Galbraith
2009-11-23 10:28 ` Alan Cox
2009-11-23 11:31 ` Alan Cox
2009-11-23 11:48 ` Ingo Molnar [this message]
2009-11-23 11:59 ` Alan Cox
2009-11-23 12:04 ` Ingo Molnar
2009-11-23 13:34 ` Alan Cox
2009-11-23 17:48 ` Ingo Molnar
2011-07-09 6:29 ` Robert Swan
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=20091123114845.GC25575@elte.hu \
--to=mingo@elte.hu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=swan.r.l@gmail.com \
--cc=torvalds@linux-foundation.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.