Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
5fbf8563
Commit
5fbf8563
authored
Nov 16, 2010
by
Jens Axboe
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'for-2.6.38/rc2-holder' into for-2.6.38/core
parents
a0205634
bdc85df7
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
27 additions
and
4 deletions
+27
-4
Documentation/cgroups/blkio-controller.txt
Documentation/cgroups/blkio-controller.txt
+27
-0
block/blk-cgroup.c
block/blk-cgroup.c
+0
-4
No files found.
Documentation/cgroups/blkio-controller.txt
View file @
5fbf8563
...
@@ -89,6 +89,33 @@ Throttling/Upper Limit policy
...
@@ -89,6 +89,33 @@ Throttling/Upper Limit policy
Limits for writes can be put using blkio.write_bps_device file.
Limits for writes can be put using blkio.write_bps_device file.
Hierarchical Cgroups
====================
- Currently none of the IO control policy supports hierarhical groups. But
cgroup interface does allow creation of hierarhical cgroups and internally
IO policies treat them as flat hierarchy.
So this patch will allow creation of cgroup hierarhcy but at the backend
everything will be treated as flat. So if somebody created a hierarchy like
as follows.
root
/ \
test1 test2
|
test3
CFQ and throttling will practically treat all groups at same level.
pivot
/ | \ \
root test1 test2 test3
Down the line we can implement hierarchical accounting/control support
and also introduce a new cgroup file "use_hierarchy" which will control
whether cgroup hierarchy is viewed as flat or hierarchical by the policy..
This is how memory controller also has implemented the things.
Various user visible config options
Various user visible config options
===================================
===================================
CONFIG_BLK_CGROUP
CONFIG_BLK_CGROUP
...
...
block/blk-cgroup.c
View file @
5fbf8563
...
@@ -1452,10 +1452,6 @@ blkiocg_create(struct cgroup_subsys *subsys, struct cgroup *cgroup)
...
@@ -1452,10 +1452,6 @@ blkiocg_create(struct cgroup_subsys *subsys, struct cgroup *cgroup)
goto
done
;
goto
done
;
}
}
/* Currently we do not support hierarchy deeper than two level (0,1) */
if
(
parent
!=
cgroup
->
top_cgroup
)
return
ERR_PTR
(
-
EPERM
);
blkcg
=
kzalloc
(
sizeof
(
*
blkcg
),
GFP_KERNEL
);
blkcg
=
kzalloc
(
sizeof
(
*
blkcg
),
GFP_KERNEL
);
if
(
!
blkcg
)
if
(
!
blkcg
)
return
ERR_PTR
(
-
ENOMEM
);
return
ERR_PTR
(
-
ENOMEM
);
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment