public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [PATCH] Use tty_schedule in VT code.
Date: Tue, 17 Jul 2007 15:06:47 -0600	[thread overview]
Message-ID: <469D2F67.40305@microgate.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707172050180.9131@pentafluge.infradead.org>

James Simmons wrote:
> Because sometimes you do want the delay. In other parts of the tty 
> code we do delay. What should be done is 

Correct, so we must stick with the delayed work structure
which requires calling the delayed work function.

>         if (tty->low_latency)
>                 flush_to_ldisc(&tty->buf.work.work);
>         else
>                 schedule_delayed_work(&tty->buf.work, 1);
> 
> Is this acceptable to you?

That does not make sense to me.

If you are calling from interrupt context, you do not want
to call flush_to_ldisc() directly regardless of low_latency.
This used to be the way it was done and it ended up causing
deadlocks in just that situation.

And the initial schedule has no reason to add the extra delay.

-- 
Paul Fulghum
Microgate Systems, Ltd.

  parent reply	other threads:[~2007-07-17 20:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 18:37 [PATCH] Use tty_schedule in VT code James Simmons
2007-07-17 18:49 ` Samuel Thibault
2007-07-17 19:17   ` James Simmons
2007-07-17 20:31     ` Paul Fulghum
2007-07-17 19:24 ` Linus Torvalds
2007-07-17 20:35   ` Paul Fulghum
2007-07-17 19:44     ` Linus Torvalds
2007-07-17 19:52       ` James Simmons
2007-07-17 20:42         ` Linus Torvalds
2007-07-17 23:35           ` Alan Cox
2007-07-18 18:17           ` James Simmons
2007-07-18 18:27             ` Paul Fulghum
2007-07-18 19:57               ` James Simmons
2007-07-18 21:12                 ` Paul Fulghum
2007-07-18 20:08               ` Linus Torvalds
2007-07-18 21:36                 ` Alan Cox
2007-07-17 21:06         ` Paul Fulghum [this message]
2007-07-17 20:15           ` James Simmons
2007-07-17 21:33             ` Paul Fulghum
2007-07-18 17:19               ` James Simmons
  -- strict thread matches above, loose matches on Subject: below --
2007-05-08 20:10 James Simmons
2007-05-08 20:32 ` Paul Fulghum
2007-05-09 20:58   ` Paul Fulghum
2007-05-09 20:56     ` James Simmons
2007-05-09 23:02       ` Paul Fulghum

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=469D2F67.40305@microgate.com \
    --to=paulkf@microgate.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox