From: David Barto <david@kdbarto.org>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] A Reiser tour de force
Date: Fri, 1 Apr 2022 10:15:11 -0700 [thread overview]
Message-ID: <44FEFAE6-720F-4449-84DB-228B7A6C097C@kdbarto.org> (raw)
In-Reply-To: <CAKH6PiVu9GVoEpao=Ammiw_t8whf=yw8Ok49cQRDm1JDQ1x7dA@mail.gmail.com>
> On Apr 1, 2022, at 8:59 AM, Douglas McIlroy <douglas.mcilroy@dartmouth.edu> wrote:
>
> The recent discussion about Research choosing BSD's paging over
> Reiser-London's brought to mind a stunning program by Reiser that
> Research did adopt.
>
> A critical primitive in the Blit terminal was bitblt (block transfer
> of a rectangular area). It was used ubiquitously, for example to
> refresh data when window-stacking changed, to move data within a
> window, or to pop up a menu.. The display memory was word-oriented, so
> bitblt was fraught with niggling details about bit alignment and
> overlap of source and destination. A general bitblt subroutine was a
> rats' nest of conditionals--grossly inefficient for important special
> cases like scrolling.
>
> Bitblt got refined (i.e. elaborated) several times before Reiser did
> away with it entirely. Instead he wrote a just-in-time generator of
> optimal code. Thousands of distinct variants, which varied in size
> from 16 to 72 bytes, could be produced by the same 400 lines of
> assembler code.
>
> Doug
Does this exist for the rest of us to study?
David
next prev parent reply other threads:[~2022-04-01 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 15:59 Douglas McIlroy
2022-04-01 17:15 ` David Barto [this message]
2022-04-01 17:26 ` Jon Steinhart
2022-04-01 19:41 ` Steffen Nurpmeso
2022-04-01 21:29 ` Rob Pike
2022-04-01 21:31 ` Rob Pike
2022-04-01 21:43 ` Jon Steinhart
2022-04-03 11:22 Paul Ruizendaal via TUHS
2022-04-03 12:24 ` Rob Pike
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=44FEFAE6-720F-4449-84DB-228B7A6C097C@kdbarto.org \
--to=david@kdbarto.org \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=tuhs@minnie.tuhs.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).