Hi,
On 23/08/18 11:56, luca abeni wrote:
> Hi Juri,
>
> sorry for the late reply (I am just back from vacations), and thanks
> for cc-ing me.
Welcome back! :-)
> I see you opened a bug on github about this, so I am going to add more
> details there,
I use github issues to keep track of things, but I guess mailing list
discussions are to be preferred though (so that more people can
potentially follow).
> but basically I think that in order to use SCHED_DEADLINE as non-root
> we need to:
> 1) Disable the boosting mechanism (not the inheritance, just the "soft
> enforcement behaviour" of tasks holding mutexes)
But then what is a sane inheritance mechanism? Walk the chain and find
the next potential deadline to inherit for the current boosted (still
runtime enforced) task before throttling it? Not sure it's going to be
any easier than the proxy solution. :-/
> 2) Implement some mechanism to limit the amount of dl bandwidth a user
> can allocate to itself (I think the cgroup-based approach we
> discussed some time ago should be OK... If I remember well, you even
> had a patch implementing it :)
I think most (all?) distributions today run with CONFIG_RT_GROUP_SCHED
disabled, we should also think about a solution that doesn't rely on
that interface. Maybe the existing system wide sched_rt_{period,
runtime}_us are enough?
Best,
- Juri
