Shall fix all of the cosmetics and repost.
WRT the magic number 34 milisecs: It was to have a "1 milisec buffer over a
33-fps" type workload which was how the
issue was found in the first place (it was a workload that had hundreds of
these 33-fps contexts running and thats why
the impact was
On 8/15/2022 09:01, Alan Previn wrote:
From: Matthew Brost
Add a delay, configurable via debugs (default 34ms), to disable
debugs -> debugfs
scheduling of a context after the pin count goes to zero. Disable
scheduling is a somewhat costly operation so the idea is that a delay
costly
From: Matthew Brost
Add a delay, configurable via debugs (default 34ms), to disable
scheduling of a context after the pin count goes to zero. Disable
scheduling is a somewhat costly operation so the idea is that a delay
allows the user to resubmit something before doing this operation.
This
From: Matthew Brost
Add a delay, configurable via debugs (default 34ms), to disable
scheduling of a context after the pin count goes to zero. Disable
scheduling is a somewhat costly operation so the idea is that a delay
allows the user to resubmit something before doing this operation.
This
On 6/27/2022 22:51, Alan Previn wrote:
From: Matthew Brost
Add a delay, configurable via debugs (default 100ms), to disable
debugs -> debugfs
Default is now 34ms?
scheduling of a context after the pin count goes to zero. Disable
scheduling is somewhat costly operation so the idea is a
From: Matthew Brost
Add a delay, configurable via debugs (default 100ms), to disable
scheduling of a context after the pin count goes to zero. Disable
scheduling is somewhat costly operation so the idea is a delay allows
the resubmit something before doing this operation. This delay is only
done
