commit d38ee8f9efeca2229ed97fbc40b65108c1be9977
author Stefan Bossbaly <stefanbossbaly@google.com> Wed Aug 31 21:04:38 2022 +0000
committer releases-try-builder <releases-try-builder@fuchsia-infra.iam.gserviceaccount.com> Thu Sep 01 16:55:59 2022 +0000
tree 1eab47dafbbaf1d9a94c5baa11ef70ef60698fdc
parent bf6d9a2ffce0727e1e899b172238077a6e04c78c

[amlogic] Adjust deadline parameters

The amlogic deadline parameters are too stringent which causes a lot of
thread context switching. Some of the tasks need more cpu time inorder
for them to accomplish in their deadline. The rationale for each change
is explained below:

vdec_irq: The HandleInterrupt was running out of CPU time which caused
it to have to be rescheduled. Generally deference is given to
interrupt routines and, so long as there operations are not
computational complex, they should be allowed to finish their
operations within one time slice.

h264_core: In steady state h264_core thread is only triggered when new
input is received and just pumps or reschedules the decoder. During
startup the first input packet received does have a cold startup period
so add a bit more CPU time to allow the thread to make progress without
getting descheduled.

Bug: 103225
Bug: b/235629262
Change-Id: I6e2170dba9a54f567855d1d2d6cab48e00310742
Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/695492
Reviewed-by: John Bauman <jbauman@google.com>
Commit-Queue: Stefan Bossbaly <stefanbossbaly@google.com>
(cherry picked from commit c6eac81363d892d1eff6c1ec9a678ecda49ae90a)