Am 13.03.23 um 17:43 schrieb Rob Clark:
On Mon, Mar 13, 2023 at 9:15 AM Christian König
wrote:
Am 13.03.23 um 15:45 schrieb Rob Clark:
On Mon, Mar 13, 2023 at 12:19 AM Christian König
wrote:
Am 11.03.23 um 18:35 schrieb Rob Clark:
From: Rob Clark
Avoid allocating memory in job_run() by em
On Mon, Mar 13, 2023 at 9:15 AM Christian König
wrote:
>
> Am 13.03.23 um 15:45 schrieb Rob Clark:
> > On Mon, Mar 13, 2023 at 12:19 AM Christian König
> > wrote:
> >> Am 11.03.23 um 18:35 schrieb Rob Clark:
> >>> From: Rob Clark
> >>>
> >>> Avoid allocating memory in job_run() by embedding the
Am 13.03.23 um 15:45 schrieb Rob Clark:
On Mon, Mar 13, 2023 at 12:19 AM Christian König
wrote:
Am 11.03.23 um 18:35 schrieb Rob Clark:
From: Rob Clark
Avoid allocating memory in job_run() by embedding the fence in the
submit object. Since msm gpu fences are always 1:1 with msm_gem_submit
w
On Mon, Mar 13, 2023 at 12:19 AM Christian König
wrote:
>
> Am 11.03.23 um 18:35 schrieb Rob Clark:
> > From: Rob Clark
> >
> > Avoid allocating memory in job_run() by embedding the fence in the
> > submit object. Since msm gpu fences are always 1:1 with msm_gem_submit
> > we can just use the fe
Am 11.03.23 um 18:35 schrieb Rob Clark:
From: Rob Clark
Avoid allocating memory in job_run() by embedding the fence in the
submit object. Since msm gpu fences are always 1:1 with msm_gem_submit
we can just use the fence's refcnt to track the submit. And since we
can get the fence ctx from the
From: Rob Clark
Avoid allocating memory in job_run() by embedding the fence in the
submit object. Since msm gpu fences are always 1:1 with msm_gem_submit
we can just use the fence's refcnt to track the submit. And since we
can get the fence ctx from the submit we can just drop the msm_fence
str
