From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] was 8½ slow and that lead to rio?
Date: Wed, 30 Jan 2002 23:15:08 -0500 [thread overview]
Message-ID: <775745f40ef7301d2ca881ff8ecb6472@plan9.bell-labs.com> (raw)
You should be able to accomplish the same
effect by allocating a window with allocwindow
for each layer. Have a look at /sys/src/libdraw/menuhit.c
for one example, or at rio for a more complicated
but perhaps clearer example. Then the kernel will handle the layers
and you should see the performance you expect.
Russ
next reply other threads:[~2002-01-31 4:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 4:15 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-31 5:37 [9fans] was 8½ " okamoto
2002-01-31 5:04 Russ Cox
2002-01-31 4:58 okamoto
2002-01-31 4:57 okamoto
2002-01-31 4:10 okamoto
2002-01-31 3:48 Russ Cox
2002-01-31 1:47 okamoto
2002-01-30 16:18 rob pike
2002-01-30 15:55 Fco.J.Ballesteros
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=775745f40ef7301d2ca881ff8ecb6472@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).