On Fri, 18 Mar 2005 14:43:38 -0500
Daniel Phillips <[EMAIL PROTECTED]> wrote:
> > You don't want to access the graphics card on every task switch.
> > On a current linux system you have something between 100 and 2000
> > context switches per second. If you do something like this, then
> > the driver has to intercept every access and check whether
> > the registers need to be swapped.
>
> Actually, this is something I'd like to think about for the future. I would
> like to see the GPU supported by the task switch just like a numeric
> co-processor. This is a lazy switch: a task that isn't using the
> co-processor doesn't pay any penalty. There are significant
> synchronization advantages to doing things that way.
What kind of advantages ?
> On the other hand, it
> is a fairly deep kernel hack, and we have other things to worry about.
> Plus, we really ought to have some functioning hardware first.
It is some kernel hack, but i don't think it would be
too complicated. The kernel already needs already some infrastructure
to handle these kind of things. We would just need to add another
item there.
But i agree, we should leave this for the second stage of our
design.
Attila Kinali
--
éãåããéãåã
_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)
