On Thu, Jul 02, 2015 at 12:54:27PM +0100, Chris Wilson wrote: > However, that equally applies to the existing request->seqno. That can > also be assigned on submission so that it always an ordered timeline, and > so can be used internally or externally. Hmm, we need to preallocate seqno space for the request during i915_gem_request_alloc(). In the noop scheduler, we are then safe to assign the next available. A reordering scheduler can insert whatever commands it needs in between batches and wouldn't need to do anything in the preallocate. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx