From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Chunyan Zhang <zhang.lyra@gmail.com>
Subject: Re: [PATCH v1 0/3] serial: Do not count XON/XOFF in the statistics
Date: Thu, 4 Apr 2024 18:54:38 +0300 [thread overview]
Message-ID: <Zg7NPnpFXkQWJ-Ks@smile.fi.intel.com> (raw)
In-Reply-To: <573aac92-9c9b-427b-a76f-3c0b7c3b6ce6@kernel.org>
On Thu, Apr 04, 2024 at 07:16:55AM +0200, Jiri Slaby wrote:
> On 04. 04. 24, 0:15, Andy Shevchenko wrote:
> > Wed, Apr 03, 2024 at 05:46:14PM +0300, Andy Shevchenko kirjoitti:
> > > Some drivers count XON/XOFF in the Tx statistics, some do not.
> > > I actually a bit uncertain, but I _think_ the correct way is not
> > > to count them, hence this series.
> >
> > Okay, it seems there are much more drivers doing that. Perhaps we need
> > to add that to the rest in this case (i.o.w. invert the series from removal
> > to addition)?
>
> Interesting, perhaps cut & paste?
>
> XON and XOFF are overhead IMO. So should not be counted. When they are, they
> mangle statistics as in transmitted (real) bytes per second.
>
> How are they handled on the RX side?
It took me a while.
All serial drivers accept everything and those that care, update statics for
anything they receive. This is because of layering. The Rx XON/XOFF seems
(note I am completely unfamiliar with mysterious ways of TTY layers) to be
handled on TTY level by n_tty_receive_char_flow_ctrl(), i.o.w. we may not
skip counting it easily.
Now the question is, shall we count the control characters on output or not?
Whatever decision we made, we should document (if not yet) and align drivers
accordingly.
Another Q is what do books / other OS / projects usually do with them
WRT statistics?
If we count everything on a wire, then we must count them, otherwise
it depends on how we treat them.
P.S.
This series as is should be abandoned. But we may continue discussing topic
under this cover letter.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-04-04 15:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 14:46 [PATCH v1 0/3] serial: Do not count XON/XOFF in the statistics Andy Shevchenko
2024-04-03 14:46 ` [PATCH v1 1/3] serial: core: Don't " Andy Shevchenko
2024-04-03 14:46 ` [PATCH v1 2/3] serial: fsl_lpuart: " Andy Shevchenko
2024-04-03 14:46 ` [PATCH v1 3/3] serial: sprd: " Andy Shevchenko
2024-04-03 22:15 ` [PATCH v1 0/3] serial: Do not " Andy Shevchenko
2024-04-04 5:16 ` Jiri Slaby
2024-04-04 15:54 ` Andy Shevchenko [this message]
2024-04-09 13:46 ` Greg Kroah-Hartman
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=Zg7NPnpFXkQWJ-Ks@smile.fi.intel.com \
--to=andy.shevchenko@gmail.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=zhang.lyra@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