Re: [PATCH v2 0/4] have the vt console preserve unicode characters

[Alan Cox <gnomes@lxorguk.ukuu.org.uk>]

On Fri, 22 Jun 2018 12:28:17 -0400 (EDT)
Nicolas Pitre <nicolas.pitre@linaro.org> wrote:

> On Fri, 22 Jun 2018, Alan Cox wrote:
> 
> > > The other point is a quite pointless assumption that existing scrollback is
> > > "optimized".  Even vgacon mostly uses software scrollback these days, as the
> > > amount of VGA display memory is really small.  
> > 
> > All of our console driver code is horribly unoptimized for most of
> > todays hardware. Long ago I did look at what was needed but it's a
> > seriously non-trivial change. In particular
> > 
> > - Console I/O occurs under enough locks to keep fort knox safe. That
> >   means it's very very hard to accelerate
> > 
> > - The logic is plain wrong for a lot of modern video. We shouldn't be
> >   scrolling, we should be rendering the current backing text buffer at
> >   video refresh rate or similar and if the source of the updates outruns
> >   us it doesn't matter - we don't have to draw all the glyphs as if we
> >   were fast enough they would have been a blur anyway.  
> 
> My executive summary from what you say is that there is no longer an 
> advantage to maintain a central vga-style glyph buffer in the core 
> console code, right?

Yeah. The only driver that it suits is the VGA text mode driver, which at
2GHz+ is going to be fast enough whatever format you convert from. We
have the memory, the processor power and the fact almost all our displays
are bitmapped (or more complex still) all in favour of throwing away that
limit.

Alan