On Sat, 2007-12-22 at 07:59 +0100, Thomas Hellström wrote: > The way I would do this with a small extension to the current > implementation is to > implement a DRM_I915_FENCE_TYPE_READ fence type and a > DRM_I915_FENCE_TYPE_WRITE fence type, which are triggered by the > corresponding buffer object proposed_flags.
Every fence would be READ|WRITE -- some of the buffers are read and some are written. The access mode is not specific to the fence, rather it is specific to the combination of the fence and each associated buffer. > This scheme would not work is a buffer is validated for READ and WRITE > at the same time, and there might be better solutions. The needed > changes to the current implementation are minimal, though. In a given command stream, it's certainly possible to mix read and write operations, although under GL that's less likely. For an X server though, it's extremely likely, so requiring any kind of synchronization to switch from write to read would be bad. -- [EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. 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
