-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Stephane Marchesin wrote:
| Yes, that was really my point. If the memory manager we use (whatever | it is) does not allow this kind of behaviour, that'll force all cards | to use a kernel-validated command submission model, which might not be | too fast, and more difficult to implement on such hardware. | | I'm not in favor of having multiple memory managers, but if the chosen | one is both slower and more complex to support in the future, that'll | be a loss for everyone. Unless we want to have another memory manager | implementation in 2 years from now... I honestly don't see a problem with having multiple memory managers. We have different hardware with different functionality and different performance characteristics. The probability of one memory manager fitting everywhere is nil. Quite frankly, the fact that it has take this long to get *anything* upstream is already failure. This is open source. Release early, release often. If something gets implemented and doesn't work out, you redo it. You don't spend forever trying to get it perfect before you release anything. :( -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFIMKYQX1gOwKyEAw8RAi1VAKCgqq+/CYZ6hsClb1dvM8jl3kzyEACgmWDE RSjrMTWUTp5w2gKDkybkGYs= =amAU -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
