From: Dusty Mabe <dusty@dustymabe.com>
To: Jiri Slaby <jslaby@suse.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: multiplexing /dev/console to all console= entries
Date: Wed, 7 Nov 2018 16:34:05 -0500 [thread overview]
Message-ID: <81094a73-c277-99cd-190b-37c25db5f7ab@dustymabe.com> (raw)
In-Reply-To: <955a0492-bab0-59d3-d01d-bea096c6e40f@suse.cz>
On 11/7/18 4:03 AM, Jiri Slaby wrote:
> On 05. 11. 18, 2:45, Dusty Mabe wrote:
>> If a patch were submitted to enable this type of behavior would such a
>> patch be acceptable? Maybe it could be a compile time option and also
>> have a kernel arg option to enable/disable it.
>
> Hi,
>
> it might kill the system on some setups where people specify more serial
> (or similarly slow consoles). Output to some console is so slow that the
> system does nothing else than writing to the consoles. What might work
> as the first step to check it out is adding a flag to the console=
> option which would mark a console as a /dev/console device too and
> multiplex only those specified by the user. Then let's see how it goes
> with userspace logging out in the wild...
>
Thanks Jiri!
I think that seems reasonable. Do you have a good idea of what you'd like it
to look like? Some options
- console=ttyS0,primary
- console=ttyS0,mux
- console=ttyS0+
- consolex=ttyS0
These are ideas. Bad ones, probably. But just throwing out ideas.
Dusty
prev parent reply other threads:[~2018-11-07 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 1:45 multiplexing /dev/console to all console= entries Dusty Mabe
2018-11-07 9:03 ` Jiri Slaby
2018-11-07 21:34 ` Dusty Mabe [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=81094a73-c277-99cd-190b-37c25db5f7ab@dustymabe.com \
--to=dusty@dustymabe.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@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).