All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: Is tty->receive_room no longer usable w/ SMP?
Date: Thu, 13 Feb 2014 19:46:35 +0000 (UTC)	[thread overview]
Message-ID: <ldj7er$ec0$1@ger.gmane.org> (raw)
In-Reply-To: 52FD187C.8020604@hurleysoftware.com

On 2014-02-13, Peter Hurley <peter@hurleysoftware.com> wrote:
> On 02/13/2014 01:50 PM, Grant Edwards wrote:

>> For example, it turns out almost nobody on the planet uses IXANY. It
>> got left out of both our automated and manual regression testing, and
>> (embarassingly) it took 10+ years for somebody to realize that it
>> didn't work.  And that "somebody" was a customer that still had 2.4
>> kenels running in production machines.
>
> Not unusual. The N_TTY ldisc just had a bug fixed in 3.10 where
> turning off IXON with an already-stopped tty permanently hung the
> tty.

Yea, over the years, Xon/Xoff flow control is probably a larger source
of headaches than any other feature.  In fact, I think our serial core
drivers currently have to disable the UART's hardware Xon/Xoff
handling because the serial core API doesn't notify the driver when
the user makes a termios call to change the Xon/Xoff characters.  [Not
that anybody really uses that feature either...]

> We should extend the serial-core to add rx methods that work with
> your UARTs in their fastest and most native way. The idea behind
> serial-core is only to abstract the busy-work away from the i/o, not
> become an ill-fitting shoe that enforces The One True Way.

The prepare/push flip buffer API was pretty close to ideal.

It eliminates one set of buffer copy operations involved in the
room/insert/push method.  But, given the speed of in-memory buffer
copies, I doubt the difference is noticeable.

-- 
Grant Edwards               grant.b.edwards        Yow! for ARTIFICIAL
                                  at               FLAVORING!!
                              gmail.com            


  reply	other threads:[~2014-02-13 19:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12 22:43 Is tty->receive_room no longer usable w/ SMP? Grant Edwards
2014-02-13  1:04 ` Peter Hurley
2014-02-13  2:27   ` Grant Edwards
2014-02-13  3:56     ` Peter Hurley
2014-02-13  5:38       ` Grant Edwards
2014-02-13 15:30         ` Peter Hurley
2014-02-13 17:52           ` Grant Edwards
2014-02-13 18:20             ` Peter Hurley
2014-02-13 18:50               ` Grant Edwards
2014-02-13 19:09                 ` Peter Hurley
2014-02-13 19:46                   ` Grant Edwards [this message]
2014-02-14 22:31             ` Grant Edwards

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='ldj7er$ec0$1@ger.gmane.org' \
    --to=grant.b.edwards@gmail.com \
    --cc=linux-serial@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.