From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <c00df855ea06874e29c9d62673719a7d@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue,  9 Jun 2009 19:36:39 -0400
To: 9fans@9fans.net
In-Reply-To: <f75780240906091629m51e3227dt6c5bc8886f20829e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: Re: [9fans] faster vesa driver
Topicbox-Message-UUID: 08623546-ead5-11e9-9d60-3106f5b1d025

On Tue Jun  9 19:30:32 EDT 2009, me@acm.jhu.edu wrote:
> > On Tue Jun  9 17:20:12 EDT 2009, geoff@plan9.bell-labs.com wrote:
> >> I've just pushed out kernel sources and binaries to incorporate
> >> Aki's mtrr and vesa changes.  The combination makes monitor=vesa
> >> run quite a bit faster; we saw a factor of three speed improvement
> >> in one case.
>
> What got three times faster? Do you have some kind of tool to measure
> draw performance overall?

using andrey's screen saver hacks, i measured about an even greater
speedup using PAT, a technique similar to mtrrs but one that
uses page tables and not fixed physical ranges.  i did my tests with
andrey's xscreensaver hacks and timing catting large files to a fixed-sized
window.

i would attribute the perf difference between PAT and mtrr to be
a function of measurement and hardware — as in my crappy hardware.
if someone sees that one or the other is faster on the same hardware,
that would be very interesting to me.

- erik