On Tue, Aug 16, 2016 at 04:07:38PM +0200, Peter Zijlstra wrote: > On Wed, Aug 10, 2016 at 06:09:44PM -0400, Johannes Weiner wrote: > > > [ That, and a disturbing number of emotional outbursts against > > systemd, which has nothing to do with any of this. ] > > Oh, so I'm entirely dreaming this then: > > https://github.com/systemd/systemd/pull/3905 > > Completely unrelated. Yes and no. We certainly do use systemd (kind of hard not to at this point if you're using any major distribution), and we do feed back the changes we make to it upstream. But this is updating systemd to work with the resource control design choices we made in the kernel, not the other way round. As I wrote to Mike before, we have been running into these resource control issues way before systemd, when we used a combination of libcgroup and custom hacks to coordinate the jobs on the system. The cgroup2 design choices fell out of experiences with those setups. Neither the problem statement nor the proposed solutions depend on systemd, which is why I had hoped we could focus these cgroup2 debates around the broader resource control issues we are trying to address, rather than get hung up on one contentious user of the interface. > Also, the argument there seems unfair at best, you don't need cpu-v2 for > buffered write control, you only need memcg and block co-mounted. Yes, memcg and block agreeing is enough for that case. But I mentioned a whole bunch of these examples, to make the broader case for a common controller model. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
