From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933289AbcCHQvs (ORCPT ); Tue, 8 Mar 2016 11:51:48 -0500 Received: from mail-yw0-f175.google.com ([209.85.161.175]:36329 "EHLO mail-yw0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933164AbcCHQuZ (ORCPT ); Tue, 8 Mar 2016 11:50:25 -0500 Date: Tue, 8 Mar 2016 11:50:22 -0500 From: Tejun Heo To: lizefan@huawei.com, hannes@cmpxchg.org Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@fb.com Subject: Re: [PATCHSET cgroup/for-4.6] cgroup: update migration destination cgroup handling Message-ID: <20160308165022.GB3447@mtj.duckdns.org> References: <1457025602-4193-1-git-send-email-tj@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1457025602-4193-1-git-send-email-tj@kernel.org> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 03, 2016 at 12:19:58PM -0500, Tejun Heo wrote: > cgroup migrations used to always be single destination. There could > be multiple sources but there was only one destination cgroup. This > changed with default hierarchy as enabling a controller would move > processes in child cgroups into separate csses. This was developed > over time and is working correctly now but the way multiple > destinations are handled is hacky and fragile. This patchset updates > migration logic so that multi-destination handling is integral. > > This patchset contains the following four patches. > > 0001-cgroup-fix-incorrect-destination-cgroup-in-cgroup_up.patch > 0002-cgroup-move-migration-destination-verification-out-o.patch > 0003-cgroup-make-cgroup-_taskset-_migrate-take-cgroup_roo.patch > 0004-cgroup-use-css_set-mg_dst_cgrp-for-the-migration-tar.patch These changes are mostly mechanical and I want them to be in for-4.6 for a while before the merge window opens up. Applying to cgroup/for-4.6. In the unlikely case that this breaks something, let's fix with followup patches. Thanks. -- tejun