9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Venkatesh Srinivas <me@acm.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] faster vesa driver
Date: Tue,  9 Jun 2009 19:29:12 -0400	[thread overview]
Message-ID: <f75780240906091629m51e3227dt6c5bc8886f20829e@mail.gmail.com> (raw)
In-Reply-To: <1943f45852005fee3e64a228e74f967f@quanstro.net>

> 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?

(I ask because I'm currently working on a 'drawperf', some that runs
tests similar to x11perf and xrender on drawing speed, but I'm stuck
and was hoping something like this exists....)

>> It's still limited to a single processor, but we've got someone
>> investigating ways to fix that.

We have rsc's 8i in contrib; would executing VESA BIOS operations in
it be the best way to support MP?

Thanks very much!
-- vs



  reply	other threads:[~2009-06-09 23:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 21:18 geoff
2009-06-09 21:26 ` erik quanstrom
2009-06-09 23:29   ` Venkatesh Srinivas [this message]
2009-06-09 23:36     ` erik quanstrom
2009-06-09 23:54 ` Kenji Arisawa
2009-06-10  0:22 ` Skip Tavakkolian
2009-06-12  9:26 ` Balwinder S Dheeman
2009-06-12 11:33   ` erik quanstrom
2009-06-12 21:42   ` James Tomaschke
2009-06-16  0:20 ` Kenji Arisawa
2009-06-16  2:19   ` erik quanstrom
2009-06-16  2:46     ` Venkatesh Srinivas
2009-06-16  3:17       ` Ori Bernstein

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=f75780240906091629m51e3227dt6c5bc8886f20829e@mail.gmail.com \
    --to=me@acm.jhu.edu \
    --cc=9fans@9fans.net \
    /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).