From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Johan Hovold <johan@kernel.org>,
Crescent Hsieh <crescentcy.hsieh@moxa.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 4/4] usb: serial: mxuport: add sysfs control for UART FIFO
Date: Wed, 13 May 2026 10:48:59 +0200 [thread overview]
Message-ID: <2026051321-apply-charting-150e@gregkh> (raw)
In-Reply-To: <agQ0RRpE27ComUnV@hovoldconsulting.com>
On Wed, May 13, 2026 at 10:20:21AM +0200, Johan Hovold wrote:
> On Tue, May 12, 2026 at 07:28:19PM +0800, Crescent Hsieh wrote:
> > On Thu, May 07, 2026 at 05:59:05PM +0200, Johan Hovold wrote:
> > > On Tue, Mar 24, 2026 at 11:50:41AM +0800, Crescent Hsieh wrote:
> > > > Add a per-port sysfs attribute, uart_fifo, to allow userspace to enable
> > > > or disable the UART FIFO at runtime.
> > >
> > > Why would you want to do that?
> > >
> > > We should try to avoid driver specific sysfs knobs.
> >
> > The motivation is to allow userspace to choose between lower latency and
> > higher throughput at runtime. Some latency-sensitive request/response
> > deployments become unreliable if the UART FIFO is enabled due to the
> > added buffering delay.
>
> Please mention this in the commit message.
Wait, no one should EVER be relying on USB for latency-sensitive
situations. USB does not guarantee this at all, and if you put a uart
in the way, like you are doing here, that just makes it even worse and
even more non-determinisitic.
Please don't think that this is even a viable solution, it is not. And
no papering over it in the kernel will ever give you the requirements
that you need, so please do not do this.
Just use a "real" uart on a PCI bus if you expect anything close to
determinism.
thanks,
greg k-h
prev parent reply other threads:[~2026-05-13 10:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260324035041.352190-1-crescentcy.hsieh@moxa.com>
[not found] ` <20260324035041.352190-2-crescentcy.hsieh@moxa.com>
2026-05-07 14:13 ` [PATCH v1 1/4] usb: serial: mxuport: add support for more MXU50U UART devices Johan Hovold
[not found] ` <20260324035041.352190-3-crescentcy.hsieh@moxa.com>
2026-05-07 14:40 ` [PATCH v1 2/4] usb: serial: mxuport: handle SEND_NEXT tx flow control Johan Hovold
[not found] ` <20260324035041.352190-4-crescentcy.hsieh@moxa.com>
2026-05-07 15:56 ` [PATCH v1 3/4] usb: serial: mxuport: support serial interface mode configuration Johan Hovold
[not found] ` <20260324035041.352190-5-crescentcy.hsieh@moxa.com>
2026-05-07 15:59 ` [PATCH v1 4/4] usb: serial: mxuport: add sysfs control for UART FIFO Johan Hovold
2026-05-12 11:28 ` Crescent Hsieh
2026-05-13 8:20 ` Johan Hovold
2026-05-13 8:48 ` Greg Kroah-Hartman [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=2026051321-apply-charting-150e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=crescentcy.hsieh@moxa.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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