* Re: [9fans] rio Peculiarities
@ 2009-02-27 22:05 Akshat Kumar
0 siblings, 0 replies; 6+ messages in thread
From: Akshat Kumar @ 2009-02-27 22:05 UTC (permalink / raw)
To: 9fans
[-- Attachment #1: Type: text/plain, Size: 42 bytes --]
echo current > /dev/wsys/%d/wctl
ak
[-- Attachment #2: Type: message/rfc822, Size: 3115 bytes --]
From: john@csplan9.rit.edu
To: 9fans@9fans.net
Subject: Re: [9fans] rio Peculiarities
Date: Fri, 27 Feb 2009 16:51:34 -0500
Message-ID: <79a364e5a34578cd32f858082fc93216@csplan9.rit.edu>
> Having a window which is `current' and `visible' but not on `top'
> gives rise to some effects of concern. For example, scrolling this
> current window is cause for massive load on the system; if there are
> windows on top, making them current requires hiding the current one
> (clicking on them is ineffective). My use for being in such a
> situation is, e.g., scrolling some acme body in the background while
> doing something with an rc window on the foreground (since my acme
> window takes up a large part of the screen).
>
>
> Not particularly important, but an interesting case nonetheless,
> ak
How exactly are you making a window current without bringing it to the
top?
John
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] rio Peculiarities
2009-02-28 0:47 Akshat Kumar
@ 2009-02-28 2:26 ` erik quanstrom
0 siblings, 0 replies; 6+ messages in thread
From: erik quanstrom @ 2009-02-28 2:26 UTC (permalink / raw)
To: 9fans
> I tried the pat patch just now, and it doesn't seem to improve the
> load or change the other effect I mentioned.
>
the pat patch is very effective for me in many situations.
however, there are some paths through the draw code
that are not optimized, or, still require large reads from
the frame buffer. and a few cards (especially nvidia
ones) have other performance problems that seem unrelated.
i get about a 10x speedup from the pat patch for most
operations. bringing a partially obscured large window to
the foreground is not one of them.
note to self: raise the priority of getting to that intel
gma driver.
- erik
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] rio Peculiarities
@ 2009-02-28 0:47 Akshat Kumar
2009-02-28 2:26 ` erik quanstrom
0 siblings, 1 reply; 6+ messages in thread
From: Akshat Kumar @ 2009-02-28 0:47 UTC (permalink / raw)
To: 9fans
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
I tried the pat patch just now, and it doesn't seem to improve the
load or change the other effect I mentioned.
ak
[-- Attachment #2: Type: message/rfc822, Size: 3061 bytes --]
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] rio Peculiarities
Date: Fri, 27 Feb 2009 17:48:40 -0500
Message-ID: <31ec63c8fe239f38e1b5b53cf8215c8b@quanstro.net>
On Fri Feb 27 16:46:34 EST 2009, akumar@mail.nanosouffle.net wrote:
> Having a window which is `current' and `visible' but not on `top'
> gives rise to some effects of concern. For example, scrolling this
> current window is cause for massive load on the system; if there are
> windows on top, making them current requires hiding the current one
> (clicking on them is ineffective). My use for being in such a
> situation is, e.g., scrolling some acme body in the background while
> doing something with an rc window on the foreground (since my acme
> window takes up a large part of the screen).
take a look at the pat patch or the older mtrr patch.
- erik
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] rio Peculiarities
2009-02-27 21:44 Akshat Kumar
2009-02-27 21:51 ` john
@ 2009-02-27 22:48 ` erik quanstrom
1 sibling, 0 replies; 6+ messages in thread
From: erik quanstrom @ 2009-02-27 22:48 UTC (permalink / raw)
To: 9fans
On Fri Feb 27 16:46:34 EST 2009, akumar@mail.nanosouffle.net wrote:
> Having a window which is `current' and `visible' but not on `top'
> gives rise to some effects of concern. For example, scrolling this
> current window is cause for massive load on the system; if there are
> windows on top, making them current requires hiding the current one
> (clicking on them is ineffective). My use for being in such a
> situation is, e.g., scrolling some acme body in the background while
> doing something with an rc window on the foreground (since my acme
> window takes up a large part of the screen).
take a look at the pat patch or the older mtrr patch.
- erik
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [9fans] rio Peculiarities
2009-02-27 21:44 Akshat Kumar
@ 2009-02-27 21:51 ` john
2009-02-27 22:48 ` erik quanstrom
1 sibling, 0 replies; 6+ messages in thread
From: john @ 2009-02-27 21:51 UTC (permalink / raw)
To: 9fans
> Having a window which is `current' and `visible' but not on `top'
> gives rise to some effects of concern. For example, scrolling this
> current window is cause for massive load on the system; if there are
> windows on top, making them current requires hiding the current one
> (clicking on them is ineffective). My use for being in such a
> situation is, e.g., scrolling some acme body in the background while
> doing something with an rc window on the foreground (since my acme
> window takes up a large part of the screen).
>
>
> Not particularly important, but an interesting case nonetheless,
> ak
How exactly are you making a window current without bringing it to the
top?
John
^ permalink raw reply [flat|nested] 6+ messages in thread
* [9fans] rio Peculiarities
@ 2009-02-27 21:44 Akshat Kumar
2009-02-27 21:51 ` john
2009-02-27 22:48 ` erik quanstrom
0 siblings, 2 replies; 6+ messages in thread
From: Akshat Kumar @ 2009-02-27 21:44 UTC (permalink / raw)
To: 9fans
Having a window which is `current' and `visible' but not on `top'
gives rise to some effects of concern. For example, scrolling this
current window is cause for massive load on the system; if there are
windows on top, making them current requires hiding the current one
(clicking on them is ineffective). My use for being in such a
situation is, e.g., scrolling some acme body in the background while
doing something with an rc window on the foreground (since my acme
window takes up a large part of the screen).
Not particularly important, but an interesting case nonetheless,
ak
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-02-28 2:26 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-02-27 22:05 [9fans] rio Peculiarities Akshat Kumar
-- strict thread matches above, loose matches on Subject: below --
2009-02-28 0:47 Akshat Kumar
2009-02-28 2:26 ` erik quanstrom
2009-02-27 21:44 Akshat Kumar
2009-02-27 21:51 ` john
2009-02-27 22:48 ` erik quanstrom
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).