RFC: Prevent submitter starvation
Context: when submitter sends a job it is scheduled by job priority, then submission time. If jobs have the same priority and single submitter sends a large batch of jobs, subsequent jobs will be stuck waiting for available device. In order not to starve submitter additional scheduling hints could be used.
Job order can be adjusted within
schedule_jobs_for_device(). To prevent submitter starvation scheduling hints could be based on active jobs.
Determining a list of unique submitters for scheduled jobs and filtering out owners of currently executed ones would allow picking a job from submitter that could potentially be starving for available device (to ensure fairness withing such group it should probably be done randomly).