linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Fulghum <paulkf@microgate.com>
To: Dick Hollenbeck <dick@softplc.com>
Cc: rmk+serial@arm.linux.org.uk, linux-serial@vger.kernel.org
Subject: Re: PROBLEM: serial port FIONREAD from realtime thread
Date: Tue, 22 Nov 2005 13:53:31 -0600	[thread overview]
Message-ID: <4383773B.1070404@microgate.com> (raw)
In-Reply-To: <43837248.5050601@softplc.com>

Dick Hollenbeck wrote:
> 1) Can you point me at the source file(s) where I can explore this 
> further? (source file the workqueue written to).

drivers/char/tty_io.c has the flip buffer code

The function tty_flip_buffer_push() is called by
the hardware driver when data has been added to
the flip buffer. This function calls flush_to_ldisc()
either directly (if low_latency is set) or indirectly
through the workqueue.

There is a problem in setting low_latency if
tty_flip_buffer_push() is called in interrupt context,
which many drivers do. You can try setting this and
seeing if your machine crashes and burns.

This code is a moving target at this time.
Alan Cox is working on bringing
a small measure of sanity to the code.

> 2) How do I determine the priority of the events kernel thread (where is 
> it created, and/or priority set).

You should be able to look at the output of
'top' or 'ps' for the 'events/0' entry.

My machine shows a priority of 10.

-- 
Paul Fulghum
Microgate Systems, Ltd.

      reply	other threads:[~2005-11-22 19:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 17:03 PROBLEM: serial port FIONREAD from realtime thread Dick Hollenbeck
2005-11-22 19:12 ` Paul Fulghum
2005-11-22 19:32   ` Dick Hollenbeck
2005-11-22 19:53     ` Paul Fulghum [this message]

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=4383773B.1070404@microgate.com \
    --to=paulkf@microgate.com \
    --cc=dick@softplc.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=rmk+serial@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).