9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ugliness in vesa
Date: Tue, 14 Jul 2009 09:23:01 -0700	[thread overview]
Message-ID: <7d3530220907140923s590847dcs2128ca4e33dcc13f@mail.gmail.com> (raw)
In-Reply-To: <87b1e377877b7285828eab6953685345@coraid.com>

On Tue, Jul 14, 2009 at 9:10 AM, erik quanstrom<quanstro@coraid.com> wrote:
>> I believe I properly applied the pat patch, but I'm not really seeing
>> any improvement. At least, it still takes fully two seconds to bring
>> one large window in front of another.
>
> that's because the screen is not double-buffered.  pat or mtrr do
> not improve reads from video memory.  there is no such thing
> as read combining.  and on some nvidia cards, especially the pcie
> ones i have, reads from video memory are really slow.

I haven't done much graphics hacking, but I remember that implementing
double buffering in the few programs I wrote was extremely easy and
gave a really cheap performance boost. Would it be similarly easy to
add double-buffering to the driver? I'm willing to put in some time,
but not too much or Ron will smack me ;)

>
>> Did you change anything with the nvidia driver when applying the mtrr
>> patch? I was under the impression that the applied patch only affected
>> the vesa driver.
>
> only the one line previously posted.  (a similar change was made to the
> vesa driver, of course.)
>
> - erik
>

As I'm reading it, the change to vganvidia.c you posted above
(re-pasted below) does pat stuff. Am I confused? I don't think pat and
mtrr are the same thing...

nv.dmabase = (void*)vmappat(scr->paddr + scr->storage - 128*1024,
128*1024, PATWT);


John
-- 
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba



  reply	other threads:[~2009-07-14 16:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13 23:57 john
2009-07-14  2:42 ` erik quanstrom
2009-07-14  5:23   ` John Floren
2009-07-14 12:06     ` erik quanstrom
2009-07-14 16:03       ` John Floren
2009-07-14 16:10         ` erik quanstrom
2009-07-14 16:23           ` John Floren [this message]
2009-07-14 16:49             ` erik quanstrom
2009-07-14  4:42 ` lucio
2009-07-14  6:24 ` cinap_lenrek

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=7d3530220907140923s590847dcs2128ca4e33dcc13f@mail.gmail.com \
    --to=slawmaster@gmail.com \
    --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).