Xref: utzoo comp.sys.att:6192 unix-pc.general:2734
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!anise!ivucsb!todd
From: todd@ivucsb.UUCP (Todd Day)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: more windows on unixpc (screen memory)
Message-ID: <757@ivucsb.UUCP>
Date: 24 Apr 89 15:40:29 GMT
References: <WJC.89Apr18182734@ho5cad.ho5cad.ATT.COM> <677@icus.islp.ny.us> <482@limbic.UUCP>
Reply-To: todd@ivucsb.UUCP (Todd Day)
Distribution: na
Organization: The Audio Club at UCSB, Isla Vista, California
Lines: 22

In article <482@limbic.UUCP> gil@limbic.UUCP (Gil Kloepfer Jr.) writes:
~So, correctly speaking, what should really happen is: 1) have AT&T increase
~the amount of windows compiled-into the window driver [a memory waste for
~those who don't use a lot of windows],

But won't the new window driver just eat more kernel memory?  It seems to me
that there is a LOT of unused kernel memory, and adding a few more window
structures doesn't seem like it will put a real drain on available kernel
memory...

BTW, when you open a window, where does the memory that holds all the
points within that window get allocated?  Certainly, there must be two
updates every time something is written to the screen (1 for the
actual screen memory and another one so the computer can do windowing).

Also, where is the screen memory mapped to?

-- 
-Todd Day-

    UUCP: {pyramid, ucbvax}!ucsbcsl!nessus!ivucsb!todd
Internet: todd%ivucsb.UUCP@anise.acc.com