All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Albert Cahalan <acahalan@gmail.com>,
	"Antonino A. Daplas" <adaplas@gmail.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	aeb@cwi.nl
Subject: Re: console font limits
Date: Thu, 03 May 2007 09:45:06 +0200	[thread overview]
Message-ID: <46399302.3050207@aitel.hist.no> (raw)
In-Reply-To: <46398D1F.1020306@zytor.com>

H. Peter Anvin wrote:
> Albert Cahalan wrote:
>   
>> Font size is not a sane place to draw the line. Features are.
>>     
>
> Font sizes are an eminently sane place to draw the line, because the
> crossover is largely determined by the point at which nailing down too
> much memory (kernel memory = unswappable memory) gets too expensive.
>   
But then the sane limit is a number of pages, not "512 glyphs".

And there is no problem if the memory is allocated dynamically
when loading the font.  Americans may then load a 127-glyph
font without wasting memory.  And those who wish to lock down
5MB unswappable memory for a hi-res chinese console can do that too.
Doing so isn't really a problem on a desktop pc.

Helge Hafting


  reply	other threads:[~2007-05-03  7:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01  4:09 console font limits Albert Cahalan
2007-05-01 11:49 ` Geert Uytterhoeven
2007-05-01 12:11   ` Antonino A. Daplas
2007-05-01 15:05     ` H. Peter Anvin
2007-05-01 15:49       ` Albert Cahalan
2007-05-02 18:02         ` Jan Engelhardt
2007-05-03  6:17           ` Albert Cahalan
2007-05-03  7:12             ` Jan Engelhardt
2007-05-03 14:14               ` Albert Cahalan
2007-05-03 14:26                 ` Jan Engelhardt
2007-05-03 15:56                   ` Geert Uytterhoeven
2007-05-03 18:27                     ` Jan Engelhardt
2007-05-03 20:15                       ` H. Peter Anvin
2007-05-03 20:16                         ` Jan Engelhardt
2007-05-04  0:17                           ` Kyle Moffett
2007-05-04  0:39                             ` H. Peter Anvin
2007-05-04  3:58                               ` Daniel Hazelton
2007-05-04  4:59                                 ` Antonino A. Daplas
2007-05-04 15:34                                   ` Jesse Barnes
2007-05-06 23:35                                     ` Daniel Hazelton
2007-05-03  7:19         ` H. Peter Anvin
2007-05-03  7:45           ` Helge Hafting [this message]
2007-05-03 10:20           ` Alan Cox
2007-05-01 17:06 ` Ken Moffat
2007-05-03 17:11 ` Andries Brouwer

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=46399302.3050207@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=acahalan@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=aeb@cwi.nl \
    --cc=geert@linux-m68k.org \
    --cc=hpa@zytor.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.