From: Grant Edwards <grant.b.edwards@gmail.com>
To: linux-serial@vger.kernel.org
Subject: Re: What's the rationale behind sending a Xoff character when the port is stopped ?
Date: Tue, 8 May 2012 14:11:39 +0000 (UTC) [thread overview]
Message-ID: <job9ir$uoc$1@dough.gmane.org> (raw)
In-Reply-To: CAES2cWxoxNG-L5hK67jH3uug9KScq=rvcqE_f+B3MaRNGDL1FA@mail.gmail.com
On 2012-05-07, Karthik Manamcheri <karthik.manamcheri@gmail.com> wrote:
> In the case when I am flow controlled (meaning I received a Xoff from
> the other end) and my receive buffer fills up, sending a Xoff to the
> other end might overflow the buffer for the other guy, right?
Not really. The Xoff doesn't go into the other guy's receive buffer.
It's processed by the flow-control software (or hardware) before it
gets to the receive buffer.
--
Grant Edwards grant.b.edwards Yow! I put aside my copy
at of "BOWLING WORLD" and
gmail.com think about GUN CONTROL
legislation...
prev parent reply other threads:[~2012-05-08 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 20:00 What's the rationale behind sending a Xoff character when the port is stopped ? Karthik Manamcheri
2012-05-07 20:50 ` Alan Cox
2012-05-07 21:47 ` Karthik Manamcheri
2012-05-08 14:11 ` Grant Edwards [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='job9ir$uoc$1@dough.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 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).