From: Manuel Schoelling <manuel.schoelling@gmx.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Mark Brown <broonie@linaro.org>,
Randy Dunlap <rdunlap@infradead.org>,
David Herrmann <dh.herrmann@gmail.com>,
Dave Airlie <airlied@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] console: Add persistent scrollback buffers for all VGA consoles
Date: Fri, 30 May 2014 16:57:43 +0200 [thread overview]
Message-ID: <1401461863.4646.9.camel@schoellingm.dzne.de> (raw)
In-Reply-To: <CAMuHMdVrDB7Q+oZi_WJk07a7OF_VOJiOHxpYwRABymTKsPuMoA@mail.gmail.com>
Hi Geert,
On Fr, 2014-05-30 at 16:28 +0200, Geert Uytterhoeven wrote:
Hi Manuel,
>
> On Fri, May 30, 2014 at 3:27 PM, Manuel Schölling
> <manuel.schoelling@gmx.de> wrote:
> > Add a scrollback buffers for each VGA console. The benefit is that
> > the scrollback history is not flushed when switching between
consoles
> > but is persistent.
> > The buffers are allocated on demand when a new console is opened.
>
> Thanks for your patch!
>
> I see two issues with this feature:
> 1. Before, the single (default 64 KiB) buffer was allocated at
startup.
> Now you will allocate a buffer each time a new console is opened.
> Depending on memory fragmentation, this may fail.
Indeed, if allocation fails, scrollbuffer[vc_num]->data will stay NULL
and scrolling will be disabled for that console. Is that ok or would you
prefer another behavior of the kernel?
> 2. People with RAM-constrained systems may not like this.
> Can it be a config option?
Sure, I will add an option for that.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 --
geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a
hacker. But
> when I'm talking to journalists I just say "programmer" or something
like that.
> -- Linus Torvalds
>
next prev parent reply other threads:[~2014-05-30 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 13:27 Manuel Schölling
2014-05-30 14:28 ` Geert Uytterhoeven
2014-05-30 14:57 ` Manuel Schoelling [this message]
2014-05-30 17:06 ` Randy Dunlap
2014-05-30 22:26 ` Jakub Wilk
2014-05-31 9:49 ` Manuel Schoelling
2016-04-23 10:07 Manuel Schölling
2016-05-02 17:59 Manuel Schölling
2016-05-09 10:39 Manuel Schölling
2016-05-16 11:25 Manuel Schölling
2016-05-23 21:07 Manuel Schölling
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=1401461863.4646.9.camel@schoellingm.dzne.de \
--to=manuel.schoelling@gmx.de \
--cc=airlied@redhat.com \
--cc=broonie@linaro.org \
--cc=dh.herrmann@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=plagnioj@jcrosoft.com \
--cc=rdunlap@infradead.org \
--cc=tomi.valkeinen@ti.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
all inboxes | Powered by JetHome®