From: "Aki Nyrhinen" <anyrhine@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] image/memimage speed
Date: Sun, 7 Dec 2008 19:00:13 +0200 [thread overview]
Message-ID: <218917ef0812070900u4f15e817nf78f2b99e83ebc75@mail.gmail.com> (raw)
In-Reply-To: <dd6fe68a0812051027t5661d7ebs81cce9a4ca0a6b7f@mail.gmail.com>
for vgavesa, you can find this on /n/sources/patch/saved/vesasoftscreen.
it's been there for a some time.
for all the cards that have support outside the vesa driver, it's probably
easiest to say monitor=vesa too, since you lose acceleration anyway.
the related mtrr or the pat patch is good to have with this, or take away
the mtrr() call from the patch.
i remember we discussed this a few years back, and you were mostly
concerned about losing accelerated ops then.
On Fri, Dec 5, 2008 at 8:27 PM, Russ Cox <rsc@swtch.com> wrote:
>> i don't think this is the case. if you recall from the original
>> post, i have used the pat registers to set up memory types on
>> a pcie card and i do see dramatic speedups for drawing to
>> the screen. however, reading from the screen is just as slow
>> as before.
>
> I think the problem of
>
>> can you explain what the downside of double-buffering
>> would be? it's not like the days where we asked, hey buddy,
>> have you got 4 megs to spare?
>
> you mean using a soft screen (a kernel copy of the video
> memory, so that you only ever write to the video card).
> double buffering is switching the screen between two
> different copies of the screen image, only ever drawing
> on the one that is not currently on the screen.
>
> in answer to your question, that might be a fine thing to do
> now that memory is more plentiful. no one has been bothered
> enough to do it. you would lose the hardware acceleration
> for fill and scroll, since you can't have the video card editing
> the frame buffer directly--your copy would be out of sync.
> on the other hand, writes are so fast that it probably wouldn't
> matter. the win for hw scroll is not reading from the frame buffer.
>
> i think it's a pretty trivial change, since the relevant code
> is all there for non-direct-mapped frame buffers anyway.
>
> go for it.
>
> russ
>
>
next prev parent reply other threads:[~2008-12-07 17:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-30 22:00 Iruata Souza
2008-11-30 23:54 ` Iruata Souza
2008-12-01 1:29 ` erik quanstrom
2008-12-01 1:54 ` andrey mirtchovski
2008-12-01 2:35 ` erik quanstrom
2008-12-01 3:30 ` andrey mirtchovski
2008-12-01 6:41 ` Paul Lalonde
2008-12-01 14:19 ` Steve Simon
2008-12-01 14:33 ` erik quanstrom
2008-12-05 6:39 ` ron minnich
2008-12-05 13:35 ` erik quanstrom
2008-12-05 18:27 ` Russ Cox
2008-12-05 18:32 ` Russ Cox
2008-12-05 18:49 ` ron minnich
2008-12-05 19:21 ` Paul Lalonde
2008-12-05 19:25 ` erik quanstrom
2008-12-05 19:30 ` Paul Lalonde
2008-12-05 19:40 ` erik quanstrom
2008-12-05 20:11 ` ron minnich
2008-12-06 5:52 ` Paul Lalonde
2008-12-07 17:00 ` Aki Nyrhinen [this message]
2008-12-07 23:22 ` erik quanstrom
2008-12-08 0:17 ` Aki Nyrhinen
2008-12-01 15:24 plalonde
2008-12-05 5:22 ` sqweek
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=218917ef0812070900u4f15e817nf78f2b99e83ebc75@mail.gmail.com \
--to=anyrhine@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).