--- John Dennis <[EMAIL PROTECTED]> wrote:
> > With a properly designed kernel driver the X server does not need
> > to map the hardware into user space and run as root.
>
> How do you efficiently control the hardware then without incuring the overhead
> of user/system transition on ioctl's? How many iotcl's and at what granularity
> are you suggesting?
>
> Are you assuming a device which can read and execute register settings from a
> memory buffer, e.g. the dma ring buffer style devices?
Of course the dma ring buffer devices are the best and decent, modern cards
implement it that way.
On modern processors the user/system transition is minor compared to the time
needed for a bitblt over the PCI bus. Doing everthing in user space was
important on a 286, but is it still a significant performance gain vs the
security issues of running X as root? You can always batch the drawing
operations to reduce the ring transition overhead. If performance is that
critical spend $35 for a DMA based card.
These arguments are different for an embedded device where everything runs as
root. Go ahead and program everything from user space to get the performance
gain. Worms and trojans aren't as big of problem for embedded devices.
=====
Jon Smirl
[EMAIL PROTECTED]
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
--
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
