linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@linux.intel.com>
To: Ivo Sieben <meltedpianoman@gmail.com>
Cc: linux-serial@vger.kernel.org, RT <linux-rt-users@vger.kernel.org>
Subject: Re: Deterministic behavior for TTY serial
Date: Thu, 19 Apr 2012 12:19:38 +0100	[thread overview]
Message-ID: <20120419121938.1215b8c1@bob.linux.org.uk> (raw)
In-Reply-To: <CAMSQXEENByqSmK2bSxMngY2WuV86AAcX_LxTbA5JSOjT3ta_FA@mail.gmail.com>

> We are wondering if it is possible to give the TTY device in more
> deterministic behavior (as in "less locks & no sleeping")
> So in case of non blocking read/write behavior:
> - We want directly write data to the serial_core transmit buffer and
> return immediately.

If you have the tty in raw mode then that is basically what the ldisc
code does (plus any flow control you may have selected).

> - Incoming data should be buffered, on a read data is read directly
> from that buffer and when no data available return immediately

Ditto in raw mode, and you can use O_NDELAY or the VMIN/VTIME fields to
optimise block transfer behaviour. We do actually do an additional
memcpy but memory copies of cached memory are so cheap it should be
irrelevant unless trying to do megabit speeds on low end embedded
processors.

> We have the idea that the default N_TTY line discipline introduces too

Based upon what analysis ?

> much overhead & locking behavior what makes it less suitable for
> deterministic serial communication on a PREEMT_RT platform.

Are you using USB ports ?

Alan

  parent reply	other threads:[~2012-04-19 11:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 14:38 Deterministic behavior for TTY serial Ivo Sieben
2012-04-19  0:14 ` Greg KH
2012-04-19 15:37   ` Ivo Sieben
2012-04-19 15:46     ` Greg KH
2012-04-26 14:27       ` Ivo Sieben
2012-05-01 14:30         ` Ivo Sieben
2012-05-01 15:04           ` Alan Cox
     [not found]             ` <CAMSQXEHAyPOF6YghsYmqqyx+N0oMgn5E=znhgFyspMUnaH78ig@mail.gmail.com>
2012-05-02  8:38               ` Ivo Sieben
2012-05-02 12:39                 ` Ivo Sieben
2012-05-03 15:28                   ` Ivo Sieben
2012-05-05  0:32                     ` Greg KH
2012-04-19 11:19 ` Alan Cox [this message]
2012-04-19 15:42   ` Ivo Sieben

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=20120419121938.1215b8c1@bob.linux.org.uk \
    --to=alan@linux.intel.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=meltedpianoman@gmail.com \
    /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).