Repository navigation
schedule: task priority levels reversal - #1269
Conversation
I've reverted level of priority tasks. Now tasks levels are as follows: - level 0 - highest priority; - level 9 - lowest priority. Signed-off-by: Bartosz Kokoszko <bartoszx.kokoszko@linux.intel.com>
|
@bkokoszx any particular reason for this ? are we aligning with posix priorities ? |
|
@bkokoszx sof/tools/topology/sof-cml-rt5682.m4 Lines 40 to 48 in 99e9f43 Now we hard code pipeline schedule to be 0, with this PR it will change from |
|
@bkokoszx I'm assigning this as P1 as it looks like it fixes a few issues suggested by @emilchudzik |
|
@lgirdwood @lgirdwood @xiulipan @ranj063 In fact we want to pipeline task be on higher priority than ipc (as it was earlier). I can revert it to "niceness" scale as it was before (-20 - highest; 0 - medium; 19 - lowest) and do not change pipelines priority (default is 0) or we can change a pipeline priority level in topology. |
|
@bkokoszx yes, pipeline should be higher priority than IPC. Do you have a PR pending to fix ? |
|
@lgirdwood |
|
@bkokoszx |
@bkokoszx this PR doesnt fix the issue entirely but it is still needed as I mentioned in issue #1263 |
|
@stevyan @ClarexZhou @keqiaozhang Please help check if this PR #1269 can fix #1263 |
I've reverted level of priority tasks. Now tasks
levels are as follows:
Signed-off-by: Bartosz Kokoszko bartoszx.kokoszko@linux.intel.com