From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: Slave buffer problem
Date: Tue, 16 Jul 1996 13:58:25 +0100 [thread overview]
Message-ID: <19960716125825.u0op_fwmoybGUILdPW5F8PAvC-dqtJ854tD6hobovHc@z> (raw)
>>I've started seeing that too, after applying the latest boddle plus the
>>devvga.c:/gscreen.ldepth patch that someone posted to the list (Is it a
>>correct fix?). ^t^tx reports that there are very few bytes free, like
>>22K (16M machine with kernerlpercent=40, vgasize=1280x1024x8). If it
the gscreen.ldepth change causes the pc implementation to behave
more like the other terminals, preallocating 3 $vgasize sized screens worth of bitmap space
(if possible) in devbit.c. this reduces the chances of being unable to create a
window (or move/reshape/hide an existing one) owing to fragmentation
of the kernel heap. kernelpercent might well need to be increased to
compensate, esp. with a screen size of 1280x1024. at home, i use kernelpercent=40
with a screen size of 1152x900x8 without much trouble.
next reply other threads:[~1996-07-16 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-16 12:58 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-07-15 14:27 philw
1996-07-15 9:18 Boyd
1996-07-15 1:41 Luther
1996-07-15 0:37 philw
1996-07-15 0:04 David
1996-07-14 23:09 Luther
1996-07-12 17:08 Luther
1996-07-12 16:33 Scott
1996-07-12 4:32 Luther
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=19960716125825.u0op_fwmoybGUILdPW5F8PAvC-dqtJ854tD6hobovHc@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).