mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: zhangqiumiao1@huawei.com, jirislaby@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] tty: resolve loopback wait problem for aging serial port
Date: Mon, 4 Jan 2021 10:09:04 +0100	[thread overview]
Message-ID: <X/LbMCeNbjedkIiy@hovoldconsulting.com> (raw)
In-Reply-To: <X+yHOr6Q5fsuQhSy@kroah.com>

On Wed, Dec 30, 2020 at 02:57:14PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Dec 30, 2020 at 09:45:29PM +0800, zhangqiumiao1@huawei.com wrote:
> > From: Qiumiao Zhang <zhangqiumiao1@huawei.com>
> > 
> > Because serial port is low-speed device, serial port writing will be suspended
> > when the buffer of driver layer is full due to serial port aging.
> 
> What do you mean here exactly?  What is "serial port aging"?
> 
> And since when is a serial port a low-speed device?  Compared to what?
> 
> > The concrete
> > representation is n_tty_write blocking in the process of wait_woken, the process
> > of writing serial port exists without feedback, and becomes a zombie process.
> 
> I do not understand this sentance, sorry.  Can you rephrase it?
> 
> > So for serial port, set the timeout value of wait_woken function to 60s. Wake up
> > and flush the buffer after timeout.
> 
> Where did the 60 second number come from?  Why that value and not any
> other specific value?
> 
> 
> > 
> > Signed-off-by: Qiumiao Zhang <zhangqiumiao1@huawei.com>
> > ---
> > v3:
> >  add changes from v1 to v2
> > 
> > v2:
> >  change to use "real name"
> >  fix wrong expression in path description
> >  remove config option
> >  use driver type to judge tty device type

Note that no mails from zhangqiumiao1@huawei.com appears to make it to
the lists so anyone not in CC only sees your replies, Greg. 

Qiumiao Zhang, you need to check your mail setup so that you can post to
the lists.

Johan

      reply	other threads:[~2021-01-04  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1609335929-13463-1-git-send-email-zhangqiumiao1@huawei.com>
2020-12-30 13:57 ` Greg KH
2021-01-04  9:09   ` Johan Hovold [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=X/LbMCeNbjedkIiy@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhangqiumiao1@huawei.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

Powered by JetHome