[LITMUS^RT] Task parameter changes during the execution of real-time task

[Jeremy Erickson]

Namhoon,

(For the rest of the list, I'm assuming this is for the RTSS paper
Namhoon is working on with me.)

If you're using budget enforcement, don't change the WCETs of any
task.  You can just make the level-A and -B jobs run for their level-B
WCETs, which is allowed by budget enforcement.  Under the experimental
setup I described, level C will mostly get starved anyway during the
overload.

I actually recommend not using budget enforcement, at least at level
C.  Don't change the WCET parameter for a job, but instead just
program the userspace code to overrun its budget.

In the situations we're trying to mimic in the experimental setup, the
problem occurs entirely in userspace, so you shouldn't be changing
parameters in the kernel.

-Jeremy Erickson

On Sun, May 11, 2014 at 6:03 PM, Namhoon Kim <namhoonk at cs.unc.edu> wrote:
> Hi,
>
> I want to change a job's WCET for a specific job_no. I tried to call
> sporadic_task_ns after the task mode was changed to LITMUS_RT_TASK. But it
> does not work. Is it possible to change task parameters after the task is
> admitted to a LITMUS real-time task?
>
> Thanks in advance,
>
> Namhoon
>
> _______________________________________________
> litmus-dev mailing list
> litmus-dev at lists.litmus-rt.org
> https://lists.litmus-rt.org/listinfo/litmus-dev
>