9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] image/memimage speed
Date: Fri,  5 Dec 2008 10:27:14 -0800	[thread overview]
Message-ID: <dd6fe68a0812051027t5661d7ebs81cce9a4ca0a6b7f@mail.gmail.com> (raw)
In-Reply-To: <39cb2be32e592403f7336c6200cf56a3@quanstro.net>

> 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


  reply	other threads:[~2008-12-05 18:27 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 [this message]
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
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=dd6fe68a0812051027t5661d7ebs81cce9a4ca0a6b7f@mail.gmail.com \
    --to=rsc@swtch.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).