9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] azerty [french] keyboard support
Date: Tue,  6 Feb 2001 12:01:14 -0500	[thread overview]
Message-ID: <200102061701.MAA25139@augusta.math.psu.edu> (raw)
In-Reply-To: <05c401c0902c$457489c0$0ab9c6d4@cybercable.fr>

In article <05c401c0902c$457489c0$0ab9c6d4@cybercable.fr> you write:
>that's a really bad idea. 2 context switches per character typed when
>all that's required is one translation table in the most extreme case
>(64k runes * 2 bytes = 128k).  obvious that sort of a table is ridiculous,
>even though 128k now isn't much, but all you need is a table (or
>set of tables) that cover all the possible scan code and store the
>matching rune.

Yeah, I thought about the context switch thing, but mentally justified
it to myself by way of figuring that keyboard input is so relatively
infrequent that it wouldn't be a big deal.

The problem with the tables in their present form is that they're not
very flexible; to change the meaning of a key, one has to rebuild the
kernel.  Well, that sucks, but the only two solutions are to add some
sort of way to change the translation tables in the kernel, or to move
keyboard processing into user land.

I'm not sure that the added complexity in the kernel is justified by
saving a couple of context switches, bearing in mind that a few million
instructions will go by between every keystroke.

Then again, I'm sure the code that Charles sent you doesn't add much
complexity to the kernel.  My fear, however, is that bloat will
eventually creep in if a bunch of such things, each not very complex in
and of itself, is added to the kernel....this is what I feel happened
to Unix.

	- Dan C.



  reply	other threads:[~2001-02-06 17:01 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06  2:05 okamoto
2001-02-06  2:13 ` Boyd Roberts
2001-02-06 11:02   ` Boyd Roberts
2001-02-06 17:01     ` Dan Cross [this message]
2001-02-06 14:57   ` Wladimir Mutel
2001-02-06 18:34     ` Theo Honohan
2001-02-09 16:49     ` Boyd Roberts
2001-02-06  5:53 ` Dan Cross
  -- strict thread matches above, loose matches on Subject: below --
2001-02-07  2:11 William Staniewicz
2001-02-06 20:52 Russ Cox
     [not found] <rob@plan9.bell-labs.com>
2001-02-06 17:11 ` rob pike
2001-02-06 19:10   ` Scott Schwartz
2001-02-06 19:23   ` Dan Cross
2001-02-06 16:44 Richard Miller
2001-02-06 16:19 rob pike
2001-02-06 13:34 William Staniewicz
2001-02-06 11:15 forsyth
2001-02-06  1:33 okamoto
2001-02-06  1:41 ` Boyd Roberts
2001-02-06  1:15 okamoto
2001-02-06  1:19 ` Boyd Roberts
2001-02-06  5:50 ` Dan Cross
2001-02-05 19:23 Ed Wishart
2001-02-06  5:20 ` Dan Cross
2001-02-05 18:55 jmk
2001-02-05 14:44 jmk
2001-02-05 18:46 ` Dan Cross
2001-02-05 19:11 ` Boyd Roberts
2001-02-06  5:11   ` Dan Cross
2001-02-05 10:34 Boyd Roberts
2001-02-05 13:07 ` paurea
2001-02-05 13:15   ` Boyd Roberts
2001-02-05 18:44 ` Dan Cross
2001-02-05  8:05 anothy
2001-02-05 18:36 ` Dan Cross
2001-02-05  7:51 Jean Mehat
2001-02-05  1:33 okamoto
2001-02-05  1:40 ` Boyd Roberts
2001-02-04  0:55 rob pike
2001-02-04  1:09 ` Boyd Roberts
2001-02-04  4:29 ` Fariborz 'Skip' Tavakkolian
2001-02-04 13:28   ` Boyd Roberts
2001-02-04 14:09   ` Boyd Roberts
2001-02-05  5:59 ` Dan Cross
2001-02-04  0:54 rob pike
2001-02-04  1:19 ` Boyd Roberts
2001-02-04  1:23   ` andrey mirtchovski
2001-02-04  1:37     ` Boyd Roberts
2001-02-03 23:40 Boyd Roberts

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=200102061701.MAA25139@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --cc=9fans@cse.psu.edu \
    /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).