Generic Process Containers (+ ResGroups/BeanCounters)
Subsystems (11)
cover Generic Process Containers (+ ResGroups/BeanCounters)
This is an update to my multi-hierarchy generic containers patch (against 2.6.19-rc6). Changes include:
- an example patch implementing the BeanCounters core and numfiles counters over generic containers. The addition of the BeanCounters code unifies the three main process grouping abstractions (Cpusets, ResGroups and BeanCounters).
- a patch splitting Cpusets into two independently groupable subsystems, Cpusets and Memsets.
- support for a subsystem to keep a container alive via refcounts (e.g. the BeanCounters numfiles counter has a reference to the beancounter object from each file charged to that beancounter, so needs to be able to keep the beancounter alive until the file is destroyed)
-------------------------------------
There have recently been various proposals floating around for resource management/accounting subsystems in the kernel, including Res Groups, User BeanCounters and others. These all need the basic abstraction of being able to group together multiple processes in an aggregate, in order to track/limit the resources permitted to those processes, and all implement this grouping in different ways.
Already existing in the kernel is the cpuset subsystem; this has a process grouping mechanism that is mature, tested, and well documented (particularly with regards to synchronization rules).
This patchset extracts the process grouping code from cpusets into a generic container system, and makes the cpusets code a client of the container system.
It also provides several example clients of the container system, including ResGroups and BeanCounters
The change is implemented in five stages plus two additional example patches:
1) extract the process grouping code from cpusets into a standalone system
2) remove the process grouping code from cpusets and hook into the container system
3) convert the container system to present a generic multi-hierarchy API, and make cpusets a client of that API
4) add a simple CPU accounting container subsystem as an example
5) example of implementing ResGroups and its numtasks controller over generic containers - not intended to be applied with this patch set
6) split cpusets into two subsystems, cpusets and memsets
7) example of implementing BeanCounters and its numfiles counter over generic containers - not intended to be applied with this patch set
The intention is that the various resource management efforts can also become container clients, with the result that:
- the userspace APIs are (somewhat) normalised
- it's easier to test out e.g. the ResGroups CPU controller in conjunction with the BeanCounters memory controller
- the additional kernel footprint of any of the competing resource management systems is substantially reduced, since it doesn't need to provide process grouping/containment, hence improving their chances of getting into the kernel
--
PATCH 1/7 Generic container system abstracted from cpusets code
This patch creates a generic process container system based on (and parallel top) the cpusets code. At a coarse level it was created by copying kernel/cpuset.c, doing s/cpuset/container/g, and stripping out any code that was cpuset-specific rather than applicable to any process container subsystem.
--- Documentation/containers.txt | 229 +++++++ fs/proc/base.c | 11 include/linux/container.h | 96 +++ include/linux/sched.h | 5 init/Kconfig | 9 init/main.c | 3 kernel/Makefile | 1 kernel/container.c | 1343 +++++++++++++++++++++++++++++++++++++++++++ kernel/exit.c | 2 kernel/fork.c | 3 10 files changed, 1699 insertions(+), 3 deletions(-)
fs/proc/base.c +9 -2
@@ -68,6 +68,7 @@#include <linux/security.h> #include <linux/ptrace.h> #include <linux/seccomp.h> +#include <linux/container.h> #include <linux/cpuset.h> #include <linux/audit.h> #include <linux/poll.h>
@@ -1782,7 +1783,10 @@ static struct pid_entry tgid_base_stuff[#ifdef CONFIG_SCHEDSTATS INF("schedstat", S_IRUGO, pid_schedstat),#endif -#ifdef CONFIG_CPUSETS +#ifdef CONFIG_CONTAINERS + REG("container", S_IRUGO, container), +#endif +#ifdef CONFIG_PROC_PID_CPUSET REG ("cpuset" ,S_IRUGO , cpuset), #endif INF("oom_score", S_IRUGO, oom_score),
@@ -2056,7 +2060,10 @@ static struct pid_entry tid_base_stuff[]#ifdef CONFIG_SCHEDSTATS INF("schedstat", S_IRUGO, pid_schedstat),#endif -#ifdef CONFIG_CPUSETS +#ifdef CONFIG_CONTAINERS + REG("container", S_IRUGO, container), +#endif +#ifdef CONFIG_PROC_PID_CPUSET REG ("cpuset" ,S_IRUGO , cpuset), #endif INF("oom_score", S_IRUGO, oom_score),
include/linux/container.h new file +96 -0
96 lines not on this page · raw message
include/linux/sched.h +4 -1
@@ -719,8 +719,8 @@ extern unsigned int max_cache_size;struct io_context ;/* See blkdev.h */ +struct container ;struct cpuset ; -#define NGROUPS_SMALL 32#define NGROUPS_PER_BLOCK ((int)(PAGE_SIZE / sizeof(gid_t)))struct group_info {
@@ -1006,6 +1006,9 @@ struct task_struct {int cpuset_mems_generation;int cpuset_mem_spread_rotor;#endif +#ifdef CONFIG_CONTAINERS +struct container *container; +#endif struct robust_list_head __user *robust_list;#ifdef CONFIG_COMPAT struct compat_robust_list_head __user *compat_robust_list;
init/Kconfig +9 -0
@@ -238,6 +238,15 @@ config IKCONFIG_PROC This option enables access to the kernel configuration file through /proc/config.gz. +config CONTAINERS + bool "Container support" + help + This option will let you create and manage process containers, + which can be used to aggregate multiple processes, e.g. for + the purposes of resource tracking. + + Say N if unsure + config CPUSETS bool "Cpuset support" depends on SMP
init/main.c +3 -0
@@ -38,6 +38,7 @@#include <linux/writeback.h> #include <linux/cpu.h> #include <linux/cpuset.h> +#include <linux/container.h> #include <linux/efi.h> #include <linux/taskstats_kern.h> #include <linux/delayacct.h>
@@ -568,6 +569,7 @@ asmlinkage void __init start_kernel(void }#endif vfs_caches_init_early (); +container_init_early ();cpuset_init_early ();mem_init ();kmem_cache_init ();
@@ -598,6 +600,7 @@ asmlinkage void __init start_kernel(void#ifdef CONFIG_PROC_FS proc_root_init ();#endif +container_init ();cpuset_init ();taskstats_init_early ();delayacct_init ();
kernel/container.c new file +1343 -0
1,343 lines not on this page · raw message
kernel/exit.c +2 -0
@@ -30,6 +30,7 @@#include <linux/taskstats_kern.h> #include <linux/delayacct.h> #include <linux/cpuset.h> +#include <linux/container.h> #include <linux/syscalls.h> #include <linux/signal.h> #include <linux/posix-timers.h>
@@ -923,6 +924,7 @@ fastcall NORET_TYPE void do_exit(long co__exit_fs (tsk);exit_thread ();cpuset_exit (tsk); +container_exit (tsk);exit_keys (tsk);if (group_dead && tsk->signal->leader)
kernel/fork.c +3 -0
@@ -31,6 +31,7 @@#include <linux/capability.h> #include <linux/cpu.h> #include <linux/cpuset.h> +#include <linux/container.h> #include <linux/security.h> #include <linux/swap.h> #include <linux/syscalls.h>
@@ -1054,6 +1055,7 @@ static struct task_struct *copy_process( p->io_context =NULL ; p->io_wait =NULL ; p->audit_context =NULL ; +container_fork (p);cpuset_fork (p);#ifdef CONFIG_NUMA p->mempolicy =mpol_copy (p->mempolicy);
@@ -1287,6 +1289,7 @@ bad_fork_cleanup_policy: bad_fork_cleanup_cpuset:#endif cpuset_exit (p); +container_exit (p); bad_fork_cleanup_delays_binfmt:delayacct_tsk_free (p);if (p->binfmt)
kernel/Makefile +1 -0
@@ -36,6 +36,7 @@ obj-$(CONFIG_PM) += power/ obj-$(CONFIG_BSD_PROCESS_ACCT) += acct.o obj-$(CONFIG_KEXEC) += kexec.o obj-$(CONFIG_COMPAT) += compat.o +obj-$(CONFIG_CONTAINERS) += container.o obj-$(CONFIG_CPUSETS) += cpuset.o obj-$(CONFIG_IKCONFIG) += configs.o obj-$(CONFIG_STOP_MACHINE) += stop_machine.o
Documentation/containers.txt new file +229 -0
229 lines not on this page · raw message
--
PATCH 2/7 Cpusets hooked into containers
In reply to [email protected]This patch removes the process grouping code from the cpusets code, instead hooking it into the generic container system. This temporarily adds cpuset-specific code in kernel/container.c, which is removed by the next patch in the series.
--- Documentation/cpusets.txt | 81 +- fs/super.c | 5 include/linux/container.h | 7 include/linux/cpuset.h | 25 include/linux/fs.h | 2 include/linux/mempolicy.h | 2 include/linux/sched.h | 4 init/Kconfig | 23 kernel/container.c | 107 +++ kernel/cpuset.c | 1273 +++++----------------------------------------- kernel/exit.c | 2 kernel/fork.c | 7 mm/oom_kill.c | 6 13 files changed, 330 insertions(+), 1214 deletions(-)
include/linux/container.h +7 -0
@@ -47,6 +47,10 @@ struct container {struct container *parent;/* my parent */ struct dentry *dentry;/* container fs entry */ + +#ifdef CONFIG_CPUSETS +struct cpuset *cpuset; +#endif };/* struct cftype:
@@ -79,6 +83,9 @@ struct cftype {int container_add_file (struct container *cont,const struct cftype *cft);int container_is_removed (const struct container *cont); +void container_set_release_agent_path (const char *path); + +int container_path (const struct container *cont,char *buf,int buflen);#else /* !CONFIG_CONTAINERS */
include/linux/cpuset.h +13 -12
@@ -11,16 +11,15 @@#include <linux/sched.h> #include <linux/cpumask.h> #include <linux/nodemask.h> +#include <linux/container.h> #ifdef CONFIG_CPUSETS -extern int number_of_cpusets;/* How many cpusets are defined in system? */ +extern int number_of_cpusets;/* How many cpusets are defined in system? */ extern int cpuset_init_early (void );extern int cpuset_init (void );extern void cpuset_init_smp (void ); -extern void cpuset_fork (struct task_struct *p); -extern void cpuset_exit (struct task_struct *p);extern cpumask_t cpuset_cpus_allowed (struct task_struct *p);extern nodemask_t cpuset_mems_allowed (struct task_struct *p);void cpuset_init_current_mems_allowed (void );
@@ -47,10 +46,6 @@ extern void __cpuset_memory_pressure_bumextern struct file_operations proc_cpuset_operations;extern char *cpuset_task_status_allowed (struct task_struct *task,char *buffer); - -extern void cpuset_lock (void ); -extern void cpuset_unlock (void ); -extern int cpuset_mem_spread_node (void );static inline int cpuset_do_page_mem_spread (void )
@@ -65,13 +60,22 @@ static inline int cpuset_do_slab_mem_sprextern void cpuset_track_online_nodes (void ); +extern int cpuset_can_attach_task (struct container *cont, +struct task_struct *tsk); +extern void cpuset_attach_task (struct container *cont, +struct task_struct *tsk); +extern void cpuset_post_attach_task (struct container *cont, +struct container *oldcont, +struct task_struct *tsk); +extern int cpuset_populate_dir (struct container *cont); +extern int cpuset_create (struct container *cont); +extern void cpuset_destroy (struct container *cont); +#else /* !CONFIG_CPUSETS */ static inline int cpuset_init_early (void ) {return 0 ; }static inline int cpuset_init (void ) {return 0 ; }static inline void cpuset_init_smp (void ) {} -static inline void cpuset_fork (struct task_struct *p) {} -static inline void cpuset_exit (struct task_struct *p) {}static inline cpumask_t cpuset_cpus_allowed (struct task_struct *p) {
@@ -110,9 +114,6 @@ static inline char *cpuset_task_status_areturn buffer; } -static inline void cpuset_lock (void ) {} -static inline void cpuset_unlock (void ) {} -static inline int cpuset_mem_spread_node (void ) {return 0 ;
kernel/exit.c +0 -2
@@ -29,7 +29,6 @@#include <linux/mempolicy.h> #include <linux/taskstats_kern.h> #include <linux/delayacct.h> -#include <linux/cpuset.h> #include <linux/container.h> #include <linux/syscalls.h> #include <linux/signal.h>
@@ -923,7 +922,6 @@ fastcall NORET_TYPE void do_exit(long co__exit_files (tsk);__exit_fs (tsk);exit_thread (); -cpuset_exit (tsk);container_exit (tsk);exit_keys (tsk);
kernel/fork.c +2 -5
@@ -30,7 +30,6 @@#include <linux/nsproxy.h> #include <linux/capability.h> #include <linux/cpu.h> -#include <linux/cpuset.h> #include <linux/container.h> #include <linux/security.h> #include <linux/swap.h>
@@ -1056,13 +1055,12 @@ static struct task_struct *copy_process( p->io_wait =NULL ; p->audit_context =NULL ;container_fork (p); -cpuset_fork (p);#ifdef CONFIG_NUMA p->mempolicy =mpol_copy (p->mempolicy);if (IS_ERR (p->mempolicy)) { retval =PTR_ERR (p->mempolicy); p->mempolicy =NULL ; - goto bad_fork_cleanup_cpuset; + goto bad_fork_cleanup_container; }mpol_fix_fork_child_flag (p);#endif
@@ -1286,9 +1284,8 @@ bad_fork_cleanup_security: bad_fork_cleanup_policy:#ifdef CONFIG_NUMA mpol_free (p->mempolicy); -bad_fork_cleanup_cpuset: +bad_fork_cleanup_container:#endif -cpuset_exit (p);container_exit (p); bad_fork_cleanup_delays_binfmt:delayacct_tsk_free (p);
kernel/container.c +100 -7
221 lines not on this page · raw message
kernel/cpuset.c +153 -1120
1,763 lines not on this page · raw message
init/Kconfig +17 -6
@@ -239,17 +239,24 @@ config IKCONFIG_PROC through /proc/config.gz. config CONTAINERS - bool "Container support" - help - This option will let you create and manage process containers, - which can be used to aggregate multiple processes, e.g. for - the purposes of resource tracking. + bool - Say N if unsure +config MAX_CONTAINER_SUBSYS + int "Number of container subsystems to support" + depends on CONTAINERS + range 1 255 + default 8 + +config MAX_CONTAINER_HIERARCHIES + int "Number of container hierarchies to support" + depends on CONTAINERS + range 2 255 + default 4 config CPUSETS bool "Cpuset support" depends on SMP + select CONTAINERS help This option will let you create and manage CPUSETs which allow dynamically partitioning a system into sets of CPUs and
@@ -258,6 +265,10 @@ config CPUSETS Say N if unsure. +config PROC_PID_CPUSET + bool "Include legacy /proc/<pid>/cpuset file" + depends on CPUSETS + config RELAY bool "Kernel->user space relay support (formerly relayfs)" help
mm/oom_kill.c +3 -3
@@ -395,7 +395,7 @@ void out_of_memory(struct zonelist *zoneshow_mem (); } -cpuset_lock (); +container_lock ();read_lock (&tasklist_lock);/*
@@ -429,7 +429,7 @@ retry:/* Found nothing?!?! Either we hang forever, or we panic. */ if (!p) {read_unlock (&tasklist_lock); -cpuset_unlock (); +container_unlock ();panic ("Out of memory and no killable processes...\n" ); }
@@ -441,7 +441,7 @@ retry: out:read_unlock (&tasklist_lock); -cpuset_unlock (); +container_unlock ();/* * Give "p" a good chance of killing itself before we
include/linux/sched.h +1 -3
@@ -720,7 +720,6 @@ extern unsigned int max_cache_size;struct io_context ;/* See blkdev.h */ struct container ; -struct cpuset ;#define NGROUPS_SMALL 32#define NGROUPS_PER_BLOCK ((int)(PAGE_SIZE / sizeof(gid_t)))struct group_info {
@@ -1001,7 +1000,6 @@ struct task_struct {short il_next;#endif #ifdef CONFIG_CPUSETS -struct cpuset *cpuset;nodemask_t mems_allowed;int cpuset_mems_generation;int cpuset_mem_spread_rotor;
@@ -1432,7 +1430,7 @@ static inline int thread_group_empty(str/* * Protects ->fs, ->files, ->mm, ->group_info, ->comm, keyring * subscriptions and synchronises with wait4(). Also used in procfs. Also -* pins the final release of task.io_context. Also protects ->cpuset. +* pins the final release of task.io_context. Also protects ->container. * * Nests both inside and outside of read_lock(&tasklist_lock). * It must not be nested with write_lock_irq(&tasklist_lock),
Documentation/cpusets.txt +31 -50
166 lines not on this page · raw message
fs/super.c +0 -5
@@ -39,11 +39,6 @@#include <linux/mutex.h> #include <asm/uaccess.h> - -void get_filesystem (struct file_system_type *fs); -void put_filesystem (struct file_system_type *fs); -struct file_system_type *get_fs_type (const char *name); -LIST_HEAD (super_blocks);DEFINE_SPINLOCK (sb_lock);
include/linux/fs.h +2 -0
@@ -1875,6 +1875,8 @@ extern int vfs_fstat(unsigned int, strucextern int vfs_ioctl (struct file *,unsigned int ,unsigned int ,unsigned long ); +extern void get_filesystem (struct file_system_type *fs); +extern void put_filesystem (struct file_system_type *fs);extern struct file_system_type *get_fs_type (const char *name);extern struct super_block *get_super (struct block_device *);extern struct super_block *user_get_super (dev_t );
include/linux/mempolicy.h +1 -1
@@ -152,7 +152,7 @@ extern void mpol_fix_fork_child_flag(str#ifdef CONFIG_CPUSETS #define current_cpuset_is_being_rebound () \ - (cpuset_being_rebound == current->cpuset) + (cpuset_being_rebound == current->container->cpuset)#else #define current_cpuset_is_being_rebound () 0#endif
--
PATCH 1/3 Miscellaneous container fixes
This patches fixes various bugs I hit in the recently posted container patches.
1. If a subsystem registers with fork/exit hook during bootup (much before rcu is initialized), then the resulting synchronize_rcu() in container_register_subsys() hangs. Avoid this by not calling synchronize_rcu() if we arent fully booted yet.
2. If cpuset_create fails() for some reason, then the resulting call to cpuset_destroy can trip. Avoid this by initializing container->...->cpuset pointer to NULL in cpuset_create().
3. container_rmdir->cpuset_destroy->update_flag can deadlock on container_lock(). Avoid this by introducing __update_flag, which doesnt take container_lock().
(I have also hit some lockdep warnings. Will post them after some review, to make sure that they are not introduced by my patches).
---
linux-2.6.19-rc6-vatsa/kernel/container.c | 4 ++- linux-2.6.19-rc6-vatsa/kernel/cpuset.c | 35 ++++++++++++++++++++++++------ 2 files changed, 31 insertions(+), 8 deletions(-)
kernel/container.c renamed from kernel/container.c~container_fixes +3 -1
@@ -1344,6 +1344,7 @@ static long container_create(struct cont cont->parent = parent; cont->root = parent->root; cont->hierarchy = parent->hierarchy; + cont->top_container = parent->top_container;for_each_subsys (cont->hierarchy, ss) { err = ss->create (ss, cont);
@@ -1580,7 +1581,8 @@ int container_register_subsys(struct conif (!need_forkexit_callback && (new_subsys->fork || new_subsys->exit)) { need_forkexit_callback =1 ; -synchronize_rcu (); +if (system_state ==SYSTEM_RUNNING ) +synchronize_rcu (); }/* If this subsystem requested that it be notified with fork
kernel/cpuset.c renamed from kernel/cpuset.c~container_fixes +28 -7
@@ -97,14 +97,22 @@ struct cpuset {/* Update the cpuset for a container */ static inline void set_container_cs (struct container *cont,struct cpuset *cs) { - cont->subsys[cpuset_subsys.subsys_id] = &cs->css; +if (cs) + cont->subsys[cpuset_subsys.subsys_id] = &cs->css; +else + cont->subsys[cpuset_subsys.subsys_id] =NULL ; }/* Retrieve the cpuset for a container */ static inline struct cpuset *container_cs (struct container *cont) { -return container_of (container_subsys_state (cont, &cpuset_subsys), - struct cpuset, css); +struct container_subsys_state *css; + + css =container_subsys_state (cont, &cpuset_subsys); +if (css) + return container_of(css, struct cpuset, css); +else +return NULL ; }/* Retrieve the cpuset for a task */
@@ -698,7 +706,7 @@ static int update_memory_pressure_enable* Call with manage_mutex held. */ -static int update_flag (cpuset_flagbits_t bit,struct cpuset *cs,char *buf) +static int __update_flag (cpuset_flagbits_t bit,struct cpuset *cs,char *buf) {int turning_on;struct cpuset trialcs;
@@ -717,18 +725,27 @@ static int update_flag(cpuset_flagbits_treturn err; cpu_exclusive_changed = (is_cpu_exclusive (cs) !=is_cpu_exclusive (&trialcs)); -container_lock ();if (turning_on)set_bit (bit, &cs->flags);else clear_bit (bit, &cs->flags); -container_unlock ();if (cpu_exclusive_changed)update_cpu_domains (cs);return 0 ; } +static int update_flag (cpuset_flagbits_t bit,struct cpuset *cs,char *buf) +{ +int err; + +container_lock (); + err =__update_flag (bit, cs, buf); +container_unlock (); + +return err; +} +/* * Frequency meter - How fast is some event occurring? *
@@ -1165,6 +1182,7 @@ int cpuset_create(struct container_subsyreturn 0 ; } parent =container_cs (cont->parent); +set_container_cs (cont,NULL ); cs =kmalloc (sizeof (*cs),GFP_KERNEL );if (!cs)return -ENOMEM ;
@@ -1202,9 +1220,12 @@ void cpuset_destroy(struct container_sub {struct cpuset *cs =container_cs (cont); +if (!cs) +return ; +cpuset_update_task_memory_state ();if (is_cpu_exclusive (cs)) { -int retval =update_flag (CS_CPU_EXCLUSIVE , cs,"0" ); +int retval =__update_flag (CS_CPU_EXCLUSIVE , cs,"0" );BUG_ON (retval); } number_of_cpusets--;
_
Signature · 2 lines
Regards, vatsa
PATCH 2/3 cpu controller (v3) - based on RTLIMIT_RT_CPU patch
Nick/Ingo,
Here's another approach for a minimal cpu controller. Would greatly
appreciate any feedback as before.
This version is inspired by Ingo's RTLIMIT_RT_CPU patches found here:
This patch is also about 80% smaller than the patches I had posted earlier:
http://lkml.org/lkml/2006/9/28/236
Primary differences between Ingo's RT_LIMIT_CPU patch and this one:
- This patch handles starvation of lower priority tasks in a group.
- This patch uses tokens for accounting cpu consumption. I didnt get good results with decaying avg approach used in the rtlimit patches.
- Task grouping based on cpuset/containers and not on rtlimit.
Other features:
- Retains one-runqueue-per-cpu, as is prevalent today
- scheduling no longer of O(1) complexity, similar to rtlimit patches. This can be avoided if we use separate runqueues for different groups (as was done in http://lkml.org/lkml/2006/9/28/236)
- Only limit supported (no guarantee)
Unsupported feature:
- SMP load balance aware of group limits. This can be handled using smpnice later if required (http://lkml.org/lkml/2006/9/28/244)
---
linux-2.6.19-rc6-vatsa/include/linux/sched.h | 3 linux-2.6.19-rc6-vatsa/kernel/sched.c | 195 ++++++++++++++++++++++++++- 2 files changed, 195 insertions(+), 3 deletions(-)
include/linux/sched.h renamed from include/linux/sched.h~cpu_ctlr +3 -0
@@ -1095,6 +1095,9 @@ static inline void put_task_struct(struc/* Not implemented yet, only for 486*/ #define PF_STARTING 0x00000002/* being created */ #define PF_EXITING 0x00000004/* getting shut down */ +#ifdef CONFIG_CPUMETER +#define PF_STARVING 0x00000010/* Task starving for CPU */ +#endif #define PF_FORKNOEXEC 0x00000040/* forked but didn't exec */ #define PF_SUPERPRIV 0x00000100/* used super-user privileges */ #define PF_DUMPCORE 0x00000200/* dumped core */
kernel/sched.c renamed from kernel/sched.c~cpu_ctlr +192 -3
291 lines not on this page · raw message
_
Signature · 2 lines
Regards, vatsa
PATCH 3/3 cpuset interface
In reply to Srivatsa VaddagiriThis patchs extends cpusets to support creation of metered cpusets. Changes made to cpusets are:
- Every cpuset directory has two new files:
cpu_meter_enabled, cpu_meter_limit
- Writing '1' into 'cpu_meter_enabled' marks the cpuset as "metered" i.e tasks in this cpuset and its child cpusets will have their CPU usage controlled by the CPU controller as per the limit settings mentioned in 'cpu_meter_limit'.
- Writing a number between 0-100 into 'cpu_meter_limit' file of a metered cpuset assigns corresponding bandwidth for all tasks in the cpuset (task-group).
- Only cpusets marked as "exclusive" can be metered.
- cpusets that have child cpusets cannot be metered.
- Metered cpusets cannot have grand-children!
Metered cpusets was discussed elaborately at:
http://lkml.org/lkml/2005/9/26/58
This patch was inspired from those discussions and is a subset of the features provided in the earlier patch.
To use this feature, apply the following patches in order (on top of 2.6.19-rc6):
http://lkml.org/lkml/2006/11/23/97 http://lkml.org/lkml/2006/11/23/99 http://lkml.org/lkml/2006/11/23/101 Patch 1/3 (in this series) Patch 2/3 (in this series) Patch 3/3 (this patch)
Enable CONFIG_CPUSETS and CONFIG_CPUMETER.
As an example, follow these steps to create metered cpusets:
# alias echo="/bin/echo"
# cd /dev # mkdir container # mount -t container container container
# cd container
# echo 1 > cpu_exclusive
# mkdir test # cd test
# echo 1 > cpus # Assign CPU3 to the cpuset. # echo 0 > mems # assign node 0 # echo 1 > cpu_exclusive # echo 1 > cpu_meter_enabled # "test" is now a "metered" cpuset
# # Because parent is marked 'cpu_meter_enabled', # # mkdir below automatically copied 'cpus', 'mems' and # # 'cpu_meter_enabled' from the parent to the new child.
# mkdir very_imp_grp
# mkdir less_imp_grp
# # Assign 70% bandwidth to very_imp_grp
# echo 70 > very_imp_grp/cpu_meter_limit
# # Assign 20% bandwidth to less_imp_grp
# echo 20 > less_imp_grp/cpu_meter_limit
# echo $very_imp_task1_pid > very_imp_grp/tasks # echo $very_imp_task2_pid > very_imp_grp/tasks
# echo $less_imp_task1_pid > less_imp_grp/tasks # echo $less_imp_task2_pid > less_imp_grp/tasks
---
linux-2.6.19-rc6-vatsa/include/linux/cpuset.h | 13 + linux-2.6.19-rc6-vatsa/include/linux/sched.h | 15 + linux-2.6.19-rc6-vatsa/init/Kconfig | 8 linux-2.6.19-rc6-vatsa/init/main.c | 4 linux-2.6.19-rc6-vatsa/kernel/cpuset.c | 222 +++++++++++++++++++++++++- linux-2.6.19-rc6-vatsa/kernel/sched.c | 86 +++++++++- 6 files changed, 343 insertions(+), 5 deletions(-)
include/linux/cpuset.h renamed from include/linux/cpuset.h~cpuset_interface +13 -0
@@ -62,6 +62,15 @@ extern void cpuset_track_online_nodes(voextern int current_cpuset_is_being_rebound (void ); +#ifdef CONFIG_CPUMETER +void *cpu_ctlr_data (struct task_struct *p); +#else +static inline void *cpu_ctlr_data (struct task_struct *p) +{ +return NULL ; +} +#endif +#else /* !CONFIG_CPUSETS */ static inline int cpuset_init_early (void ) {return 0 ; }
@@ -127,6 +136,10 @@ static inline int current_cpuset_is_beinreturn 0 ; } +static inline void *cpu_ctlr_data (struct task_struct *p) +{ +return NULL ; +}#endif /* !CONFIG_CPUSETS */ #endif /* _LINUX_CPUSET_H */
init/main.c renamed from init/main.c~cpuset_interface +2 -2
@@ -507,6 +507,8 @@ asmlinkage void __init start_kernel(voidunwind_setup ();setup_per_cpu_areas ();smp_prepare_boot_cpu ();/* arch-specific boot-cpu hooks */ +container_init_early (); +cpuset_init_early ();/* * Set up the scheduler prior starting any interrupts (such as the
@@ -569,8 +571,6 @@ asmlinkage void __init start_kernel(void }#endif vfs_caches_init_early (); -container_init_early (); -cpuset_init_early ();mem_init ();kmem_cache_init ();setup_per_cpu_pageset ();
kernel/cpuset.c renamed from kernel/cpuset.c~cpuset_interface +220 -2
336 lines not on this page · raw message
kernel/sched.c renamed from kernel/sched.c~cpuset_interface +85 -1
98 lines not on this page · raw message
include/linux/sched.h renamed from include/linux/sched.h~cpuset_interface +15 -0
@@ -1695,6 +1695,21 @@ static inline void thaw_processes(void)static inline int try_to_freeze (void ) {return 0 ; }#endif /* CONFIG_PM */ + +#ifdef CONFIG_CPUMETER +struct task_grp ; +struct task_grp_ops { +void *(*create_group)(void ); +void (*destroy_group)(struct task_grp *grp); +int (*set_limit)(struct task_grp *grp,unsigned long limit); +unsigned long (*get_limit)(struct task_grp *grp); +void (*move_task)(struct task_struct *p,struct task_grp *old, +struct task_grp *new); +}; + +extern struct task_grp_ops *cpu_ctlr; +#endif +#endif /* __KERNEL__ */ #endif
init/Kconfig renamed from init/Kconfig~cpuset_interface +8 -0
@@ -265,6 +265,14 @@ config CPUSETS Say N if unsure. +config CPUMETER + bool "CPU resource control" + depends on CPUSETS && EXPERIMENTAL + help + This options lets you create cpu resource partitions within + cpusets. Each resource partition can be given a different quota + of CPU usage. + config PROC_PID_CPUSET bool "Include legacy /proc/<pid>/cpuset file" depends on CPUSETS
_
Signature · 2 lines
Regards, vatsa
Re: [Patch 1/3] Miscellaneous container fixes
In reply to Srivatsa VaddagiriQuoted 8 lines · Srivatsa Vaddagiri
This patches fixes various bugs I hit in the recently posted container patches.
1. If a subsystem registers with fork/exit hook during bootup (much before rcu is initialized), then the resulting
synchronize_rcu()incontainer_register_subsys()hangs. Avoid this by not callingsynchronize_rcu()if we arent fully booted yet.
Quoted 7 lines
2. If
cpuset_createfails()for some reason, then the resulting call tocpuset_destroycan trip. Avoid this by initializing container->...->cpuset pointer to NULL incpuset_create().3.
container_rmdir->cpuset_destroy->update_flagcan deadlock oncontainer_lock(). Avoid this by introducing__update_flag, which doesnt takecontainer_lock().
Ah - this may be the lockup that PaulJ hit.
Thanks for these fixes.
Paul
Re: [Patch 1/3] Miscellaneous container fixes
Quoted 1 line · Paul M
Ah - this may be the lockup that PaulJ hit.
Yes - looks like this fixes it. Thanks, Srivatsa.
And with that fix, it becomes obvious how to reproduce this problem:
mount -t cpuset cpuset /dev/cpuset # if not already mounted
cd /dev/cpuset
mkdir foo
echo 1 > foo/cpu_exclusive
rmdir foo # hangs ...
However ...
Read the comment in kernel/cpuset.c for the routine cpuset_destroy(). It explains that update_flag() is called where it is (turning off the cpu_exclusive flag, if it was set), to avoid the calling sequence:
cpuset_destroy->update_flag->update_cpu_domains->lock_cpu_hotplug
while holding the callback_mutex, as that could ABBA deadlock with the CPU hotplug code.
But with this container based rewrite of cpusets, it now seems that cpuset_destroy -is- called holding the callback_mutex (though I don't see any mention of that in the cpuset_destroy comment ;), so it would seem that we once again are at risk for this ABBA deadlock.
I also notice that the comment for container_lock() in the file kernel/container.c only mentions its use in the oom code. That is no longer the only, or even primary, user of this lock routine. The kernel/cpuset.c code uses it frequently (without comment ;), and I wouldn't be surprised to see other future controllers calling container_lock() as well.
Looks like its time to update those comments, and think about what was written there before, as that might catch a bug or two, such as the one Srivatsa just fixed for us.
Most of those long locking comments in kernel/cpuset.c are there for a reason - recording the results of a lesson learned in the school of hard knocks.
Signature · 3 lines
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401Re: [Patch 1/3] Miscellaneous container fixes
Quoted 8 lines · Paul Jackson
Read the comment in
kernel/cpuset.cfor the routinecpuset_destroy(). It explains thatupdate_flag()is called where it is (turning off thecpu_exclusiveflag, if it was set), to avoid the calling sequence:
cpuset_destroy->update_flag->update_cpu_domains->lock_cpu_hotplugwhile holding the
callback_mutex, as that could ABBA deadlock with the CPU hotplug code.
This particular race is gone in the -mm2 kernel since cpus_exclusive no longer drives sched_domains - can we assume that this will be reaching mainline some time soon?
Quoted 4 lines
But with this container based rewrite of cpusets, it now seems that
cpuset_destroy-is- called holding thecallback_mutex(though I don't see any mention of that in thecpuset_destroycomment ;), so it would
And in fact I explicitly documented it as only holding manage_mutex, not callback_mutex in Documentation/containers.txt. I think maybe this slipped in during the multi-hierarchy rewrite. :-(
Looking at the various *_destroy() functions in the container subsystems in my patch set, I think that it should be OK to call the destructors prior to taking callback_mutex for the unlinking of the container from its parents.
Quoted 7 lines
I also notice that the comment for
container_lock()in the filekernel/container.conly mentions its use in the oom code. That is no longer the only, or even primary, user of this lock routine. Thekernel/cpuset.ccode uses it frequently (without comment ;), and I wouldn't be surprised to see other future controllers callingcontainer_lock()as well.
As was pointed out by Chandra Seetharaman, it would be nice if we could avoid having all the container subsystems relying on callback_mutex for their locking needs - particularly since that's likely to be acquired at performance-sensitive times.
The cpu_acct and beancounters subsystems that I included in my patch set both use their own per-container locks for synchronization, so it's not completely necessary to use the central locks. There's probably a happy medium between "one big lock" and "way too many small locks".
Paul
PATCH 3/7 Add generic multi-subsystem API to containers
In reply to [email protected]This patch removes all cpuset-specific knowlege from the container system, replacing it with a generic API that can be used by multiple subsystems. Cpusets is adapted to be a container subsystem.
--- Documentation/containers.txt | 233 ++++++++++++- include/linux/container.h | 132 +++++++ include/linux/cpuset.h | 16 include/linux/mempolicy.h | 12 include/linux/sched.h | 4 kernel/container.c | 716 +++++++++++++++++++++++++++++++++++-------- kernel/cpuset.c | 165 ++++++--- mm/mempolicy.c | 2 8 files changed, 1048 insertions(+), 232 deletions(-)
include/linux/container.h +125 -7
@@ -14,8 +14,6 @@#ifdef CONFIG_CONTAINERS -extern int number_of_containers;/* How many containers are defined in system? */ -extern int container_init_early (void );extern int container_init (void );extern void container_init_smp (void );
@@ -30,6 +28,68 @@ extern void container_unlock(void);extern void container_manage_lock (void );extern void container_manage_unlock (void ); +struct containerfs_root ; + +/* Per-subsystem/per-container state maintained by the system. */ +struct container_subsys_state { +/* The container that this subsystem is attached to. Useful +* for subsystems that want to know about the container +* hierarchy structure */ +struct container *container; + +/* State maintained by the container system to allow +* subsystems to be "busy". Should be accessed via css_get() +* and css_put() */ +spinlock_t refcnt_lock; +atomic_t refcnt; +}; + +/* +* Call css_get() to hold a reference on the container; following a +* return of 0, this container subsystem state object is guaranteed +* not to be destroyed until css_put() is called on it. A non-zero +* return code indicates that a reference could not be taken. +* +*/ + +static inline int css_get (struct container_subsys_state *css) +{ +int retval =0 ; +unsigned long flags; +/* Synchronize with container_rmdir() */ +spin_lock_irqsave (&css->refcnt_lock, flags); +if (atomic_read (&css->refcnt) >=0 ) { +/* Container is still alive */ +atomic_inc (&css->refcnt); + }else { +/* Container removal is in progress */ + retval = -EINVAL ; + } +spin_unlock_irqrestore (&css->refcnt_lock, flags); +return retval; +} + +/* +* If you are holding current->alloc_lock then it's impossible for you +* to be moved out of your container, and hence it's impossible for +* your container to be destroyed. Therefore doing a simple +* atomic_inc() on a css is safe. +*/ + +static inline void css_get_current (struct container_subsys_state *css) +{ +atomic_inc (&css->refcnt); +} + +/* +* css_put() should be called to release a reference taken by +* css_get() or css_get_current() +*/ + +static inline void css_put (struct container_subsys_state *css) { +atomic_dec (&css->refcnt); +} +struct container {unsigned long flags;/* "unsigned long" so bitops work */
@@ -46,11 +106,15 @@ struct container {struct list_head children;/* my children */ struct container *parent;/* my parent */ -struct dentry *dentry;/* container fs entry */ +struct dentry *dentry;/* container fs entry */ -#ifdef CONFIG_CPUSETS -struct cpuset *cpuset; -#endif +/* Private pointers for each registered subsystem */ +struct container_subsys_state *subsys[CONFIG_MAX_CONTAINER_SUBSYS ]; + +int hierarchy; + +struct containerfs_root *root; +struct container *top_container; };/* struct cftype:
@@ -67,8 +131,9 @@ struct container {*/ struct inode ; +#define MAX_CFTYPE_NAME 64struct cftype { -char *name; +char name[MAX_CFTYPE_NAME ];int private;int (*open) (struct inode *inode,struct file *file); ssize_t (*read) (struct container *cont, struct cftype *cft,
@@ -87,6 +152,59 @@ void container_set_release_agent_path(coint container_path (const struct container *cont,char *buf,int buflen); +/* Container subsystem type. See Documentation/containers.txt for details */ + +struct container_subsys { +int (*create)(struct container_subsys *ss, +struct container *cont); +void (*destroy)(struct container_subsys *ss,struct container *cont); +int (*can_attach)(struct container_subsys *ss, +struct container *cont,struct task_struct *tsk); +void (*attach)(struct container_subsys *ss,struct container *cont, +struct container *old_cont,struct task_struct *tsk); +void (*post_attach)(struct container_subsys *ss, +struct container *cont, +struct container *old_cont, +struct task_struct *tsk); +void (*fork)(struct container_subsys *ss,struct task_struct *task); +void (*exit)(struct container_subsys *ss,struct task_struct *task); +int (*populate)(struct container_subsys *ss, +struct container *cont); + +int subsys_id; +#define MAX_CONTAINER_TYPE_NAMELEN 32 +const char *name; + +/* Protected by RCU */ +int hierarchy; + +struct list_head sibling; +}; + +int container_register_subsys (struct container_subsys *subsys); + +static inline struct container_subsys_state *container_subsys_state ( +struct container *cont, +struct container_subsys *ss) +{ +return cont->subsys[ss->subsys_id]; +} + +static inline struct container *task_container (struct task_struct *task, +struct container_subsys *ss) +{ +return rcu_dereference (task->container[ss->hierarchy]); +} + +static inline struct container_subsys_state *task_subsys_state ( +struct task_struct *task, +struct container_subsys *ss) +{ +return container_subsys_state (task_container (task, ss), ss); +} + +int container_path (const struct container *cont,char *buf,int buflen); +#else /* !CONFIG_CONTAINERS */ static inline int container_init_early (void ) {return 0 ; }
include/linux/cpuset.h +6 -10
@@ -60,16 +60,7 @@ static inline int cpuset_do_slab_mem_sprextern void cpuset_track_online_nodes (void ); -extern int cpuset_can_attach_task (struct container *cont, -struct task_struct *tsk); -extern void cpuset_attach_task (struct container *cont, -struct task_struct *tsk); -extern void cpuset_post_attach_task (struct container *cont, -struct container *oldcont, -struct task_struct *tsk); -extern int cpuset_populate_dir (struct container *cont); -extern int cpuset_create (struct container *cont); -extern void cpuset_destroy (struct container *cont); +extern int current_cpuset_is_being_rebound (void );#else /* !CONFIG_CPUSETS */
@@ -131,6 +122,11 @@ static inline int cpuset_do_slab_mem_sprstatic inline void cpuset_track_online_nodes (void ) {} +static inline int current_cpuset_is_being_rebound (void ) +{ +return 0 ; +} +#endif /* !CONFIG_CPUSETS */ #endif /* _LINUX_CPUSET_H */
kernel/container.c +599 -117
990 lines not on this page · raw message
kernel/cpuset.c +109 -56
430 lines not on this page · raw message
Documentation/containers.txt +207 -26
274 lines not on this page · raw message
include/linux/mempolicy.h +0 -12
@@ -148,14 +148,6 @@ extern void mpol_rebind_task(struct task const nodemask_t *new);extern void mpol_rebind_mm (struct mm_struct *mm,nodemask_t *new);extern void mpol_fix_fork_child_flag (struct task_struct *p); -#define set_cpuset_being_rebound (x) (cpuset_being_rebound = (x)) - -#ifdef CONFIG_CPUSETS -#define current_cpuset_is_being_rebound () \ - (cpuset_being_rebound == current->container->cpuset) -#else -#define current_cpuset_is_being_rebound () 0 -#endif extern struct mempolicy default_policy; extern struct zonelist *huge_zonelist(struct vm_area_struct *vma,
@@ -173,8 +165,6 @@ static inline void check_highest_zone(enint do_migrate_pages (struct mm_struct *mm,const nodemask_t *from_nodes,const nodemask_t *to_nodes,int flags); -extern void *cpuset_being_rebound;/* Trigger mpol_copy vma rebind */ -#else struct mempolicy {};
@@ -253,8 +243,6 @@ static inline void mpol_fix_fork_child_f { } -#define set_cpuset_being_rebound (x) do {} while (0) -static inline struct zonelist *huge_zonelist (struct vm_area_struct *vma,unsigned long addr) {
include/linux/sched.h +2 -2
@@ -1005,7 +1005,7 @@ struct task_struct {int cpuset_mem_spread_rotor;#endif #ifdef CONFIG_CONTAINERS -struct container *container; +struct container *container[CONFIG_MAX_CONTAINER_HIERARCHIES ];#endif struct robust_list_head __user *robust_list;#ifdef CONFIG_COMPAT
@@ -1430,7 +1430,7 @@ static inline int thread_group_empty(str/* * Protects ->fs, ->files, ->mm, ->group_info, ->comm, keyring * subscriptions and synchronises with wait4(). Also used in procfs. Also -* pins the final release of task.io_context. Also protects ->container. +* pins the final release of task.io_context. Also protects ->container[]. * * Nests both inside and outside of read_lock(&tasklist_lock). * It must not be nested with write_lock_irq(&tasklist_lock),
mm/mempolicy.c +0 -2
@@ -1307,7 +1307,6 @@ EXPORT_SYMBOL(alloc_pages_current);* keeps mempolicies cpuset relative after its cpuset moves. See * further kernel/cpuset.c update_nodemask(). */ -void *cpuset_being_rebound;/* Slow path of a mempolicy copy */ struct mempolicy *__mpol_copy (struct mempolicy *old)
@@ -1906,4 +1905,3 @@ out: m->version = (vma != priv->tail_vma) ? vma->vm_start :0 ;return 0 ; } -
--
PATCH 4/7 Simple CPU accounting container subsystem
In reply to [email protected]This demonstrates how to use the generic container subsystem for a simple resource tracker that counts the total CPU time used by all processes in a container, during the time that they're members of the container.
--- include/linux/cpu_acct.h | 14 +++++ init/Kconfig | 7 ++ kernel/Makefile | 1 kernel/cpu_acct.c | 117 +++++++++++++++++++++++++++++++++++++++++++++++ kernel/sched.c | 6 ++ 5 files changed, 145 insertions(+)
include/linux/cpu_acct.h new file +14 -0
@@ -0,0 +1,14 @@ + +#ifndef _LINUX_CPU_ACCT_H +#define _LINUX_CPU_ACCT_H + +#include <linux/container.h> +#include <asm/cputime.h> + +#ifdef CONFIG_CONTAINER_CPUACCT +extern void cpuacct_charge (struct task_struct *,cputime_t cputime); +#else +static void inline cpuacct_charge (struct task_struct *p,cputime_t cputime) {} +#endif + +#endif
init/Kconfig +7 -0
@@ -269,6 +269,13 @@ config PROC_PID_CPUSET bool "Include legacy /proc/<pid>/cpuset file" depends on CPUSETS +config CONTAINER_CPUACCT + bool "Simple CPU accounting container subsystem" + select CONTAINERS + help + Provides a simple Resource Controller for monitoring the + total CPU consumed by the tasks in a container + config RELAY bool "Kernel->user space relay support (formerly relayfs)" help
kernel/cpu_acct.c new file +117 -0
117 lines not on this page · raw message
kernel/Makefile +1 -0
@@ -38,6 +38,7 @@ obj-$(CONFIG_KEXEC) += kexec.o obj-$(CONFIG_COMPAT) += compat.o obj-$(CONFIG_CONTAINERS) += container.o obj-$(CONFIG_CPUSETS) += cpuset.o +obj-$(CONFIG_CONTAINER_CPUACCT) += cpu_acct.o obj-$(CONFIG_IKCONFIG) += configs.o obj-$(CONFIG_STOP_MACHINE) += stop_machine.o obj-$(CONFIG_AUDIT) += audit.o auditfilter.o
kernel/sched.c +6 -0
@@ -52,6 +52,7 @@#include <linux/tsacct_kern.h> #include <linux/kprobes.h> #include <linux/delayacct.h> +#include <linux/cpu_acct.h> #include <asm/tlb.h> #include <asm/unistd.h>
@@ -2977,6 +2978,8 @@ void account_user_time(struct task_struc p->utime =cputime_add (p->utime, cputime); +cpuacct_charge (p, cputime); +/* Add user time to cpustat. */ tmp =cputime_to_cputime64 (cputime);if (TASK_NICE (p) >0 )
@@ -3000,6 +3003,9 @@ void account_system_time(struct task_str p->stime =cputime_add (p->stime, cputime); +if (p != rq->idle) +cpuacct_charge (p, cputime); +/* Add system time to cpustat. */ tmp =cputime_to_cputime64 (cputime);if (hardirq_count () - hardirq_offset)
--
PATCH 5/7 Resource Groups over generic containers
In reply to [email protected]This patch provides the RG core and numtasks controller as container subsystems, intended as an example of how to implement a more complex resource control system over generic process containers. The changes to the core involve primarily removing the group management, task membership and configfs support and adding interface layers to talk to the generic container layer instead.
Each resource controller becomes an independent container subsystem; the RG core is essentially a library that the resource controllers can use to provide the RG API to userspace. Rather than a single shares and stats file in each group, there's a <controller>_shares and a <controller>_stats file, each linked to the appropriate resource controller.
include/linux/moduleparam.h | 12 - include/linux/numtasks.h | 28 ++ include/linux/res_group.h | 87 ++++++++ include/linux/res_group_rc.h | 97 ++++++++ init/Kconfig | 22 ++ kernel/Makefile | 1 kernel/fork.c | 7 kernel/res_group/Makefile | 2 kernel/res_group/local.h | 38 +++ kernel/res_group/numtasks.c | 467 +++++++++++++++++++++++++++++++++++++++++++ kernel/res_group/res_group.c | 160 ++++++++++++++ kernel/res_group/rgcs.c | 302 +++++++++++++++++++++++++++ kernel/res_group/shares.c | 228 ++++++++++++++++++++ 13 files changed, 1447 insertions(+), 4 deletions(-)
include/linux/moduleparam.h +9 -3
@@ -75,11 +75,17 @@ struct kparam_array/* Helper functions: type is byte, short, ushort, int, uint, long, ulong, charp, bool or invbool, or XXX if you define param_get_XXX, param_set_XXX and param_check_XXX. */ -#define module_param_named (name, value, type, perm) \ - param_check_##type(name, &(value)); \ - module_param_call(name, param_set_##type, param_get_##type, &value, perm); \ +#define module_param_named_call (name, value, type, set, perm) \ + param_check_##type(name, &(value)); \ + module_param_call(name, set, param_get_##type, &(value), perm); \ __MODULE_PARM_TYPE(name, #type) +#define module_param_named (name, value, type, perm) \ + module_param_named_call(name, value, type, param_set_##type, perm) + +#define module_param_set_call (name, type, setfn, perm) \ + module_param_named_call(name, name, type, setfn, perm) +#define module_param (name, type, perm) \ module_param_named(name, name, type, perm)
include/linux/numtasks.h new file +28 -0
@@ -0,0 +1,28 @@ +/* numtasks.h - No. of tasks resource controller for Resource Groups +* +* Copyright (C) Chandra Seetharaman, IBM Corp. 2003, 2004, 2005 +* +* Provides No. of tasks resource controller for Resource Groups +* +* Latest version, more details at http://ckrm.sf.net +* +* This program is free software; you can redistribute it and/or modify +* it under the terms of the GNU General Public License as published by +* the Free Software Foundation; either version 2 of the License, or +* (at your option) any later version. +* +*/ +#ifndef _LINUX_NUMTASKS_H +#define _LINUX_NUMTASKS_H + +#ifdef CONFIG_RES_GROUPS_NUMTASKS +#include <linux/res_group_rc.h> + +extern int numtasks_allow_fork (struct task_struct *); + +#else /* CONFIG_RES_GROUPS_NUMTASKS */ + +#define numtasks_allow_fork (task) (0) + +#endif /* CONFIG_RES_GROUPS_NUMTASKS */ +#endif /* _LINUX_NUMTASKS_H */
include/linux/res_group.h new file +87 -0
87 lines not on this page · raw message
include/linux/res_group_rc.h new file +97 -0
97 lines not on this page · raw message
init/Kconfig +22 -0
@@ -311,6 +311,28 @@ config TASK_XACCT Say N if unsure. +menu "Resource Groups" + +config RES_GROUPS + bool "Resource Groups" + depends on EXPERIMENTAL + select CONTAINERS + help + Resource Groups is a framework for controlling and monitoring + resource allocation of user-defined groups of tasks. For more + information, please visit http://ckrm.sf.net. + +config RES_GROUPS_NUMTASKS + bool "Number of Tasks Resource Controller" + depends on RES_GROUPS + default y + help + Provides a Resource Controller for Resource Groups that allows + limiting number of tasks a resource group can have. + + Say N if unsure, Y to use the feature. + +endmenu config SYSCTL bool
kernel/Makefile +1 -0
@@ -53,6 +53,7 @@ obj-$(CONFIG_RELAY) += relay.o obj-$(CONFIG_UTS_NS) += utsname.o obj-$(CONFIG_TASK_DELAY_ACCT) += delayacct.o obj-$(CONFIG_TASKSTATS) += taskstats.o tsacct.o +obj-$(CONFIG_RES_GROUPS) += res_group/ ifneq ($(CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER),y) # According to Alan Modra <[email protected]>, the -fno-omit-frame-pointer is
kernel/fork.c +6 -1
@@ -48,6 +48,7 @@#include <linux/delayacct.h> #include <linux/taskstats_kern.h> #include <linux/random.h> +#include <linux/numtasks.h> #include <asm/pgtable.h> #include <asm/pgalloc.h>
@@ -1352,7 +1353,7 @@ long do_fork(unsigned long clone_flags, int __user *child_tidptr) {struct task_struct *p; -int trace =0 ; +int trace =0 , rc;struct pid *pid =alloc_pid ();long nr;
@@ -1365,6 +1366,10 @@ long do_fork(unsigned long clone_flags, clone_flags |=CLONE_PTRACE ; } + rc =numtasks_allow_fork (current); +if (rc) +return rc; + p =copy_process (clone_flags, stack_start, regs, stack_size, parent_tidptr, child_tidptr, nr);/* * Do this prior waking up the new thread - the thread pointer
kernel/res_group/Makefile new file +2 -0
@@ -0,0 +1,2 @@ +obj-y = res_group.o shares.o rgcs.o +obj-$(CONFIG_RES_GROUPS_NUMTASKS) += numtasks.o
kernel/res_group/local.h new file +38 -0
@@ -0,0 +1,38 @@ +/* +* Contains function definitions that are local to the Resource Groups. +* NOT to be included by controllers. +*/ + +#include <linux/res_group_rc.h> + +extern struct res_controller *get_controller_by_name (const char *); +extern struct res_controller *get_controller_by_id (unsigned int ); +extern void put_controller (struct res_controller *); +extern struct resource_group *alloc_res_group (struct resource_group *, +const char *); +extern int free_res_group (struct resource_group *); +extern void release_res_group (struct kref *); +extern int set_controller_shares (struct resource_group *, +struct res_controller *,const struct res_shares *); +/* Set shares for the given resource group and resource to default values */ +extern void set_shares_to_default (struct resource_group *, +struct res_controller *); +extern void res_group_teardown (void ); +extern int set_res_group (pid_t ,struct resource_group *); +extern void move_tasks_to_parent (struct resource_group *); + +ssize_t res_group_file_read (struct container *cont, +struct cftype *cft, +struct file *file, +char __user *buf, +size_t nbytes,loff_t *ppos); +ssize_t res_group_file_write (struct container *cont, +struct cftype *cft, +struct file *file, +const char __user *userbuf, +size_t nbytes,loff_t *ppos); + +enum { +RG_FILE_SHARES , +RG_FILE_STATS , +};
kernel/res_group/numtasks.c new file +467 -0
467 lines not on this page · raw message
kernel/res_group/res_group.c new file +160 -0
160 lines not on this page · raw message
kernel/res_group/rgcs.c new file +302 -0
302 lines not on this page · raw message
kernel/res_group/shares.c new file +228 -0
228 lines not on this page · raw message
--
PATCH 7/7 BeanCounters over generic process containers
In reply to [email protected]This patch implements the BeanCounter resource control abstraction over generic process containers. It contains the beancounter core code, plus the numfiles resource counter. It doesn't currently contain any of the memory tracking code or the code for switching beancounter context in interrupts.
Currently all the beancounters resource counters are lumped into a single hierarchy; ideally it would be possible for each resource counter to be a separate container subsystem, allowing them to be connected to different hierarchies.
--- fs/file_table.c | 11 + include/bc/beancounter.h | 192 ++++++++++++++++++++++++ include/bc/misc.h | 27 +++ include/linux/fs.h | 3 init/Kconfig | 4 init/main.c | 3 kernel/Makefile | 1 kernel/bc/Kconfig | 17 ++ kernel/bc/Makefile | 7 kernel/bc/beancounter.c | 371 +++++++++++++++++++++++++++++++++++++++++++++++ kernel/bc/misc.c | 56 +++++++ 11 files changed, 691 insertions(+), 1 deletion(-)
init/Kconfig +4 -0
@@ -601,6 +601,10 @@ config STOP_MACHINE Need stop_machine() primitive. endmenu +menu "Beancounters" +source "kernel/bc/Kconfig" +endmenu + menu "Block layer" source "block/Kconfig" endmenu
kernel/Makefile +1 -0
@@ -12,6 +12,7 @@ obj-y = sched.o fork.o exec_domain.o obj-$(CONFIG_STACKTRACE) += stacktrace.o obj-y += time/ +obj-$(CONFIG_BEANCOUNTERS) += bc/ obj-$(CONFIG_DEBUG_MUTEXES) += mutex-debug.o obj-$(CONFIG_LOCKDEP) += lockdep.o ifeq ($(CONFIG_PROC_FS),y)
kernel/bc/Kconfig new file +17 -0
@@ -0,0 +1,17 @@ +config BEANCOUNTERS + bool "Enable resource accounting/control" + default n + select CONTAINERS + help + When Y this option provides accounting and allows configuring + limits for user's consumption of exhaustible system resources. + The most important resource controlled by this patch is unswappable + memory (either mlock'ed or used by internal kernel structures and + buffers). The main goal of this patch is to protect processes + from running short of important resources because of accidental + misbehavior of processes or malicious activity aiming to ``kill'' + the system. It's worth mentioning that resource limits configured + by setrlimit(2) do not give an acceptable level of protection + because they cover only a small fraction of resources and work on a + per-process basis. Per-process accounting doesn't prevent malicious + users from spawning a lot of resource-consuming processes.
kernel/bc/Makefile new file +7 -0
@@ -0,0 +1,7 @@ +# +# kernel/bc/Makefile +# +# Copyright (C) 2006 OpenVZ SWsoft Inc. +# + +obj-y = beancounter.o misc.o
include/bc/beancounter.h new file +192 -0
192 lines not on this page · raw message
init/main.c +3 -0
@@ -52,6 +52,8 @@#include <linux/debug_locks.h> #include <linux/lockdep.h> +#include <bc/beancounter.h> +#include <asm/io.h> #include <asm/bugs.h> #include <asm/setup.h>
@@ -482,6 +484,7 @@ asmlinkage void __init start_kernel(voidchar * command_line;extern struct kernel_param __start___param[], __stop___param[]; +bc_init_early ();smp_setup_processor_id ();/*
kernel/bc/beancounter.c new file +371 -0
371 lines not on this page · raw message
include/bc/misc.h new file +27 -0
@@ -0,0 +1,27 @@ +/* +* include/bc/misc.h +* +* Copyright (C) 2006 OpenVZ SWsoft Inc +* +*/ + +#ifndef __BC_MISC_H__ +#define __BC_MISC_H__ + +struct file ; + +#ifdef CONFIG_BEANCOUNTERS +int __must_check bc_file_charge (struct file *); +void bc_file_uncharge (struct file *); +#else +static inline int __must_check bc_file_charge (struct file *f) +{ +return 0 ; +} + +static inline void bc_file_uncharge (struct file *f) +{ +} +#endif + +#endif
kernel/bc/misc.c new file +56 -0
56 lines not on this page · raw message
fs/file_table.c +10 -1
@@ -22,6 +22,8 @@#include <linux/sysctl.h> #include <linux/percpu_counter.h> +#include <bc/misc.h> +#include <asm/atomic.h> /* sysctl tunables... */
@@ -43,6 +45,7 @@ static inline void file_free_rcu(structstatic inline void file_free (struct file *f) {percpu_counter_dec (&nr_files); +bc_file_uncharge (f);call_rcu (&f->f_u.fu_rcuhead, file_free_rcu); }
@@ -107,8 +110,10 @@ struct file *get_empty_filp(void)if (f ==NULL ) goto fail; -percpu_counter_inc (&nr_files);memset (f,0 ,sizeof (*f)); +if (bc_file_charge (f)) + goto fail_charge; +percpu_counter_inc (&nr_files);if (security_file_alloc (f)) goto fail_sec;
@@ -135,6 +140,10 @@ fail_sec:file_free (f); fail:return NULL ; + + fail_charge: +kmem_cache_free (filp_cachep, f); +return NULL ; }EXPORT_SYMBOL (get_empty_filp);
include/linux/fs.h +3 -0
@@ -750,6 +750,9 @@ struct file {spinlock_t f_ep_lock;#endif /* #ifdef CONFIG_EPOLL */ struct address_space *f_mapping; +#ifdef CONFIG_BEANCOUNTERS +struct beancounter *f_bc; +#endif };extern spinlock_t files_lock;#define file_list_lock () spin_lock(&files_lock);
--
I got a chance to build and test this patch set, to see if it behaved like I expected cpusets to behave, on an ia64 SN2 Altix system.
Two details - otherwise looked good. I continue to like this approach.
The two details are (1) /proc/<pid>/cpuset not configured by default if CPUSETS configured, and (2) a locking bug wedging tasks trying to rmdir a cpuset off the notify_on_release hook.
1) I had to enable CONFIG_PROC_PID_CPUSET. I used the following one line change to do this. I am willing to consider, in due time, phasing out such legacy cpuset support. But so long as it is small stuff that is not getting in anyone's way, I think we should take our sweet time about doing so -- as in a year or two after marking it deprecated or some such. No sense deciding that matter now; keep the current cpuset API working throughout any transitition to container based cpusets, then revisit the question of whether to deprecate and eventually remove these kernel API details, later on, after the major reconstruction dust settles. In general, we try to avoid removing kernel API's, especially if they are happily being used and working and not causing anyone grief.
============================ begin ============================
init/Kconfig +1 -0
@@ -268,6 +268,7 @@ config CPUSETS config PROC_PID_CPUSET bool "Include legacy /proc/<pid>/cpuset file" depends on CPUSETS + default y if CPUSETS config CONTAINER_CPUACCT bool "Simple CPU accounting container subsystem"
============================= end =============================
2) I wedged the kernel on the container_lock, doing a removal of a cpuset using notify_on_release.
Right now, that test system has the following two tasks, wedged:
============================ begin ============================
F S UID PID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 0 S root 4992 34 0 71 -5 - 380 wait 22:51 ? 00:00:00 /bin/sh /sbin/cpuset_release_agent /cpuset_test_tree 0 D root 4994 4992 0 72 -5 - 200 contai 22:51 ? 00:00:00 rmdir /dev/cpuset//cpuset_test_tree
============================= end =============================
I had a cpuset called /cpuset_test_tree, and some sub-cpusets below it. I marked it 'notify_on_release' and then removed all tasks from it, and then removed the child cpusets that it had. Removing that last child cpuset presumably triggered the above callout to /sbin/cpuset_release_agent, which called rmdir.
That wait address (from /proc/4994/stat) in hex is a0000001000f1060, and my System.map has the two lines:
a0000001000f1040 T container_lock a0000001000f1360 T container_manage_unlock
So it is wedged in container_lock.
I have subsequently also wedged an 'ls' command trying to scan this /dev/cpuset directory, waiting in the kernel routine vfs_readdir (not surprising, given that I'm in the middle of doing a rmdir on that directory.)
If you don't immediately see the problem, I can go back and get a kernel stack trace or whatever else you need.
This lockup occurred the first, and thus far only, time that I tried to use notify_on_release to rmdir a cpuset. So I presume it is an easy failure for me to reproduce.
Signature · 3 lines
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401Quoted 5 lines · Paul Jackson
config
PROC_PID_CPUSET
bool "Include legacy /proc/<pid>/cpuset file" depends on CPUSETS
+ default y if CPUSETS
Sounds very reasonable.
Quoted 3 lines
2) I wedged the kernel on the
container_lock, doing a removal of a cpuset usingnotify_on_release.
I guess I've not really tested doing interesting things from the notify_on_release code, just checked that it successfully executed a simple command. I'll look into it.
Thanks for the feedback.
Paul
Quoted 3 lines · Paul Jackson
2) I wedged the kernel on the
container_lock, doing a removal of a cpuset usingnotify_on_release.
I couldn't reproduce this, with a /sbin/cpuset_release_agent that does:
#!/bin/bash
logger cpuset_release_agent $1
rmdir /dev/cpuset/$1
and running the commands:
while true; do
mkdir -p /dev/cpuset/bar/foo
echo 1 > /dev/cpuset/bar/notify_on_release
rmdir /dev/cpuset/bar/foo
usleep 1000
done
Is it actually reproducible for you? If so, could you get a fuller backtrace?
Thanks,
Paul