> Note that before this patch, someone trying to get a new job for an FB
> that already has a job running would actually get the old job object
> and might start messing up with it. Not sure that's what we want.
I don't think that's what we want either, and I think I took pains to
ensure this woul
On Fri, 2 Aug 2019 08:00:28 -0700
Alyssa Rosenzweig wrote:
> What happens if the CPU creates jobs significiantly faster than the GPU
> processes them? Could you have four jobs for the same framebuffer in
> flight at once?
That's probably what will happen, yes.
>
> At present, we do some heavy
What happens if the CPU creates jobs significiantly faster than the GPU
processes them? Could you have four jobs for the same framebuffer in
flight at once?
At present, we do some heavy flushing so "no" but in the future we'll
want to lax up for performance.
On Fri, Aug 02, 2019 at 12:12:50PM +02
This guarantees that new draws targetting the same framebuffer will
get a new job instance.
Signed-off-by: Boris Brezillon
---
src/gallium/drivers/panfrost/pan_job.c | 8
1 file changed, 8 insertions(+)
diff --git a/src/gallium/drivers/panfrost/pan_job.c
b/src/gallium/drivers/panfrost
