9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Anton.Pavlovetsky" <pavlovetsky@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] ctrl radeon: not working for ATI Radeon 9600 Mobility?
Date: Tue,  4 May 2010 08:47:10 +0000	[thread overview]
Message-ID: <0a85bdc0-336c-41ca-9673-c8b17fe8dc16@37g2000yqm.googlegroups.com> (raw)
In-Reply-To: <n2qf75780241005011548q2a5f80b5hf570f8bd1b81514c@mail.gmail.com>

On May 2, 3:56 am, quans...@quanstro.net (erik quanstrom) wrote:
> On Sat May  1 18:50:38 EDT 2010, m...@endeavour.zapto.org wrote:
>
> > > [...] the main slowdown
> > > is reading from the hardware framebuffer, which plan 9 does a lot.
>
> > Where in the draw path does Plan 9 read back from the framebuffer? Why so much?
>
> /sys/src/9/port/devdraw.c:/^drawchar and multiple places in :/^drawmesg
>
> - erik

Okay, now let me generalize the discussion a little bit and ask what
do you think how the graphical performance can be achieved in
principle (on Plan 9). You say processor speed has little to do with
it: the bottleneck is how it interacts with hardware. Is the model of
interaction implemented in /sys/src/9/port/devdraw.c is okay or needs
to be changed? Or the devdraw.c is okay and this is the incomplete
driver which slows us? Is there a third way? What the third way? - let
me show you the case, not the exact replica of what I mean, but
something along the lines.
Before linuxemu emerged, the question of getting a variety of software
to work on Plan 9 was resolved in many ways and many times. First,
there is APE - an organized, if little theoretical system to port
software. Then, the attempts to port significant projects and make
them work natively: like X server and GCC. Then, VNC, which is said to
be "more then enough". We cannot forget an idea to port qemu. The
trend is to avoid to port and maintain the code and, instead to
produce the solution which works universally.
What I am trying to figure out is how to avoid the hardware specifics,
escape the driver bottlenecks, virtualize the whole thing and make it
work universally. I mean: maybe performance through specific driver
plus specific hardware is obsolete.



  parent reply	other threads:[~2010-05-04  8:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d7a540d6-2751-4e30-8766-e3511bb8c202@g11g2000yqe.googlegroups.co>
2010-04-26 13:15 ` erik quanstrom
2010-04-29  9:58 ` Anton.Pavlovetsky
     [not found] ` <7caa7a0a-fb6d-4ffa-81ef-ad3256100f2c@g21g2000yqk.googlegroups.co>
2010-04-29 11:17   ` erik quanstrom
2010-04-29 12:44     ` Venkatesh Srinivas
2010-04-30  8:53     ` Anton.Pavlovetsky
2010-04-30  8:53   ` Anton.Pavlovetsky
     [not found]   ` <9e5fc5ec-43d5-4cf3-be92-3fc8c4829ba0@l32g2000yqm.googlegroups.co>
2010-04-30 12:07     ` erik quanstrom
2010-04-30 12:30       ` Gabriel Díaz
2010-05-01 13:53         ` Venkatesh Srinivas
2010-05-01 14:08           ` erik quanstrom
2010-05-01 19:05             ` Venkatesh Srinivas
2010-05-01 22:48       ` Venkatesh Srinivas
2010-05-02  0:42         ` erik quanstrom
2010-05-04  8:47         ` Anton.Pavlovetsky [this message]
2010-04-26 11:17 Anton.Pavlovetsky

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=0a85bdc0-336c-41ca-9673-c8b17fe8dc16@37g2000yqm.googlegroups.com \
    --to=pavlovetsky@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).