All of lore.kernel.org
 help / color / mirror / Atom feed
From: yulei.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org,
	hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
	christian-STijNZzMWpgWenYVfaLwtA@public.gmane.org
Cc: cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	benbjiang-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org,
	kernellwp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	lihaiwei.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	linussli-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org,
	herberthbli-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org,
	lennychen-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org,
	allanyuliu-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org,
	Yulei Zhang <yuleixzhang-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org>
Subject: [RFC 0/1] Introduce new attribute "priority" to control group
Date: Sun,  4 Apr 2021 22:51:53 +0800	[thread overview]
Message-ID: <cover.1617355387.git.yuleixzhang@tencent.com> (raw)

From: Yulei Zhang <yuleixzhang-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org>

This patch is the init patch of a series which we want to present the idea
of prioritized tasks management. As the cloud computing introduces intricate
configurations to provide customized infrasturctures and friendly user
experiences, in order to maximum utilization of sources and improve the
efficiency of arrangement, we add the new attribute "priority" to control
group, which could be used as graded factor by subssystems to manipulate
the behaviors of processes.

Base on the order of priority, we could apply different resource configuration
strategies, sometimes it will be more accuracy instead of fine tuning in each
subsystem. And of course to set fundamental rules, for example, high priority
cgroups could seize the resource from cgroups with lower priority all the time.

The default value of "priority" is set to 0 which means the highest
priority, and the totally levels of priority is defined by
CGROUP_PRIORITY_MAX. Each subsystem could register callback to receive the
priority change notification for their own purposes. 

We would like to send out the corresponding features in the coming weeks,
which are relaying on the priority settings. For example, the prioritized
oom, memory reclaiming and cpu schedule strategy.

Lei Chen (1):
  cgroup: add support for cgroup priority

 include/linux/cgroup-defs.h |  2 +
 include/linux/cgroup.h      |  2 +
 kernel/cgroup/cgroup.c      | 90 +++++++++++++++++++++++++++++++++++++
 3 files changed, 94 insertions(+)

-- 
2.28.0


             reply	other threads:[~2021-04-04 14:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 14:51 yulei.kernel-Re5JQEeQqe8AvxtiuMwx3w [this message]
     [not found] ` <cover.1617355387.git.yuleixzhang-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org>
2021-04-04 14:52   ` [RFC 1/1] cgroup: add support for cgroup priority yulei.kernel-Re5JQEeQqe8AvxtiuMwx3w
2021-04-04 17:46     ` kernel test robot
2021-04-04 17:29   ` [RFC 0/1] Introduce new attribute "priority" to control group Tejun Heo
2021-04-08 16:49     ` yulei zhang
     [not found]       ` <CACZOiM0xA+6kAeM2sk3SfVV9Vu+5dOzC7APoNmB0Zw3jQKbg+w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-04-08 20:58         ` Shakeel Butt

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=cover.1617355387.git.yuleixzhang@tencent.com \
    --to=yulei.kernel-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=allanyuliu-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org \
    --cc=benbjiang-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org \
    --cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=christian-STijNZzMWpgWenYVfaLwtA@public.gmane.org \
    --cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
    --cc=herberthbli-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org \
    --cc=kernellwp-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=lennychen-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org \
    --cc=lihaiwei.kernel-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linussli-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.org \
    --cc=lizefan.x-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org \
    --cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=yuleixzhang-1Nz4purKYjRBDgjK7y7TUQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.