Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1601309

Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller

From Patrick Bellasi <patrick.bellasi@arm.com>
Newsgroups linux.kernel
Subject Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller
Date 2017-03-15 12:30 +0100
Message-ID <tlfhU-6UD-13@gated-at.bofh.it> (permalink)
References <tfRge-5JN-31@gated-at.bofh.it> <tfRpT-5QG-1@gated-at.bofh.it> <tkvI5-7IV-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 13-Mar 03:46, Joel Fernandes (Google) wrote:
> On Tue, Feb 28, 2017 at 6:38 AM, Patrick Bellasi
> <patrick.bellasi@arm.com> wrote:
> > The CPU CGroup controller allows to assign a specified (maximum)
> > bandwidth to tasks within a group, however it does not enforce any
> > constraint on how such bandwidth can be consumed.
> > With the integration of schedutil, the scheduler has now the proper
> > information about a task to select  the most suitable frequency to
> > satisfy tasks needs.
> [..]
> 
> > +static u64 cpu_capacity_min_read_u64(struct cgroup_subsys_state *css,
> > +                                    struct cftype *cft)
> > +{
> > +       struct task_group *tg;
> > +       u64 min_capacity;
> > +
> > +       rcu_read_lock();
> > +       tg = css_tg(css);
> > +       min_capacity = tg->cap_clamp[CAP_CLAMP_MIN];
> 
> Shouldn't the cap_clamp be accessed with READ_ONCE (and WRITE_ONCE in
> the write path) to avoid load-tearing?

tg->cap_clamp is an "unsigned int" and thus I would expect a single
memory access to write/read it, isn't it? I mean: I do not expect the
compiler "to mess" with these accesses.

However, if your concerns are more about overlapping read/write for the
same capacity from different threads, then perhaps we should better
use a mutex to serialize these two functions... not entirely convinced...

> Thanks,
> Joel

-- 
#include <best/regards.h>

Patrick Bellasi

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU  controller Patrick Bellasi <patrick.bellasi@arm.com> - 2017-03-15 12:30 +0100
  Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU controller Joel Fernandes <joelaf@google.com> - 2017-03-15 14:30 +0100
    Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU  controller "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2017-03-15 17:20 +0100
      Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU  controller Patrick Bellasi <patrick.bellasi@arm.com> - 2017-03-15 17:50 +0100
        Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU  controller "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2017-03-15 18:30 +0100
          Re: [RFC v3 1/5] sched/core: add capacity constraints to CPU  controller Patrick Bellasi <patrick.bellasi@arm.com> - 2017-03-15 19:00 +0100

csiph-web