public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	cgroups@vger.kernel.org
Subject: [GIT PULL] cgroup changes for 4.3
Date: Wed, 2 Sep 2015 08:42:43 -0400	[thread overview]
Message-ID: <20150902124243.GD22326@mtj.duckdns.org> (raw)

Hello,

cgroup changes for 4.3.

* A new PIDs controller is added.  It turns out that PIDs are actually
  an independent resource from kmem due to the limited PID space.

* More core preparations for the v2 interface.  Once cpu side
  interface is settled, it should be ready for lifting the devel mask.
  for-4.3-unified-base was temporarily branched so that other trees
  (block) can pull cgroup core changes that blkcg changes depend on.

* A non-critical idr_preload usage bug fix.

Thanks.

The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:

  Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git for-4.3

for you to fetch changes up to 20f1f4b5ffb870631bf4a4e7c7ba10e3528ae6a6:

  Merge branch 'for-4.3-unified-base' into for-4.3 (2015-08-25 14:19:29 -0400)

----------------------------------------------------------------
Aleksa Sarai (4):
      cgroup: allow a cgroup subsystem to reject a fork
      cgroup: implement the PIDs subsystem
      cgroup: add documentation for the PIDs controller
      cgroup: pids: fix invalid get/put usage

Tejun Heo (6):
      cgroup: define controller file conventions
      cgroup: export cgrp_dfl_root
      cgroup: make cftype->private a unsigned long
      cgroup: don't print subsystems for the default hierarchy
      cgroup: introduce cgroup_subsys->legacy_name
      Merge branch 'for-4.3-unified-base' into for-4.3

Vladimir Davydov (1):
      cgroup: fix idr_preload usage

 CREDITS                                     |   5 +
 Documentation/cgroups/00-INDEX              |   2 +
 Documentation/cgroups/pids.txt              |  85 +++++++
 Documentation/cgroups/unified-hierarchy.txt |  80 ++++++-
 include/linux/cgroup-defs.h                 |  15 +-
 include/linux/cgroup.h                      |  24 +-
 include/linux/cgroup_subsys.h               |  28 +++
 init/Kconfig                                |  16 ++
 kernel/Makefile                             |   1 +
 kernel/cgroup.c                             | 122 ++++++++--
 kernel/cgroup_freezer.c                     |   2 +-
 kernel/cgroup_pids.c                        | 355 ++++++++++++++++++++++++++++
 kernel/fork.c                               |  17 +-
 kernel/sched/core.c                         |   2 +-
 14 files changed, 717 insertions(+), 37 deletions(-)
 create mode 100644 Documentation/cgroups/pids.txt
 create mode 100644 kernel/cgroup_pids.c

-- 
tejun

                 reply	other threads:[~2015-09-02 12:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150902124243.GD22326@mtj.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox