[lkml]   [2018]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 2/3] drm/scheduler: Don't call wait_event_killable for signaled process.

On 04/25/2018 08:01 PM, Eric W. Biederman wrote:
> Andrey Grodzovsky <> writes:
>> On 04/25/2018 01:17 PM, Oleg Nesterov wrote:
>>> On 04/25, Andrey Grodzovsky wrote:
>>>> here (drm_sched_entity_fini) is also a bad idea, but we still want to be
>>>> able to exit immediately
>>>> and not wait for GPU jobs completion when the reason for reaching this code
>>>> is because of KILL
>>>> signal to the user process who opened the device file.
>>> Can you hook f_op->flush method?
>> But this one is called for each task releasing a reference to the the file, so
>> not sure I see how this solves the problem.
> The big question is why do you need to wait during the final closing a
> file?
> The wait can be terminated so the wait does not appear to be simply a
> matter of correctness.

Well, as I understand it, it just means that you don't want to abruptly
terminate GPU work in progress without a good
reason (such as KILL signal). When we exit we are going to release
various resources GPU is still using so we either
wait for it to complete or terminate the remaining jobs.


> Eric

 \ /
  Last update: 2018-04-26 14:34    [W:0.142 / U:2.984 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site