On Sun, 3 Oct 2010 23:57:56 -0700
Greg Thelen gthe...@google.com wrote:
Add additional flags to page_cgroup to track dirty pages
within a mem_cgroup.
Signed-off-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
Signed-off-by: Andrea Righi ari...@develer.com
Signed-off-by: Greg Thelen
On Sun, 3 Oct 2010 23:57:57 -0700
Greg Thelen gthe...@google.com wrote:
Document cgroup dirty memory interfaces and statistics.
Signed-off-by: Andrea Righi ari...@develer.com
Signed-off-by: Greg Thelen gthe...@google.com
Nice.
Acked-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
On Sun, 3 Oct 2010 23:57:58 -0700
Greg Thelen gthe...@google.com wrote:
Replace usage of the mem_cgroup_update_file_mapped() memcg
statistic update routine with two new routines:
* mem_cgroup_inc_page_stat()
* mem_cgroup_dec_page_stat()
As before, only the file_mapped statistic is
On Sun, 3 Oct 2010 23:58:01 -0700
Greg Thelen gthe...@google.com wrote:
Add calls into memcg dirty page accounting. Notify memcg when pages
transition between clean, file dirty, writeback, and unstable nfs.
This allows the memory controller to maintain an accurate view of
the amount of its
On Sun, 3 Oct 2010 23:57:59 -0700
Greg Thelen gthe...@google.com wrote:
If pages are being migrated from a memcg, then updates to that
memcg's page statistics are protected by grabbing a bit spin lock
using lock_page_cgroup(). In an upcoming commit memcg dirty page
accounting will be
KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com writes:
On Sun, 3 Oct 2010 23:57:58 -0700
Greg Thelen gthe...@google.com wrote:
Replace usage of the mem_cgroup_update_file_mapped() memcg
statistic update routine with two new routines:
* mem_cgroup_inc_page_stat()
*
On Sun, 3 Oct 2010 23:58:02 -0700
Greg Thelen gthe...@google.com wrote:
Extend mem_cgroup to contain dirty page limits. Also add routines
allowing the kernel to query the dirty usage of a memcg.
These interfaces not used by the kernel yet. A subsequent commit
will add kernel calls to
KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com writes:
On Sun, 3 Oct 2010 23:57:59 -0700
Greg Thelen gthe...@google.com wrote:
If pages are being migrated from a memcg, then updates to that
memcg's page statistics are protected by grabbing a bit spin lock
using lock_page_cgroup(). In an
On Sun, 3 Oct 2010 23:58:03 -0700
Greg Thelen gthe...@google.com wrote:
Add cgroupfs interface to memcg dirty page limits:
Direct write-out is controlled with:
- memory.dirty_ratio
- memory.dirty_bytes
Background write-out is controlled with:
- memory.dirty_background_ratio
On Sun, 3 Oct 2010 23:58:04 -0700
Greg Thelen gthe...@google.com wrote:
The determine_dirtyable_memory() function is not used outside of
page writeback. Make the routine static. No functional change.
Just a cleanup in preparation for a change that adds memcg dirty
limits consideration into
On Sun, 3 Oct 2010 23:58:00 -0700
Greg Thelen gthe...@google.com wrote:
Add memcg routines to track dirty, writeback, and unstable_NFS pages.
These routines are not yet used by the kernel to count such pages.
A later change adds kernel calls to these new routines.
Signed-off-by: Greg
KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com writes:
On Sun, 3 Oct 2010 23:58:03 -0700
Greg Thelen gthe...@google.com wrote:
Add cgroupfs interface to memcg dirty page limits:
Direct write-out is controlled with:
- memory.dirty_ratio
- memory.dirty_bytes
Background
On Sun, 3 Oct 2010 23:58:05 -0700
Greg Thelen gthe...@google.com wrote:
If the current process is in a non-root memcg, then
global_dirty_limits() will consider the memcg dirty limit.
This allows different cgroups to have distinct dirty limits
which trigger direct and background writeback at
KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com writes:
On Sun, 3 Oct 2010 23:58:00 -0700
Greg Thelen gthe...@google.com wrote:
Add memcg routines to track dirty, writeback, and unstable_NFS pages.
These routines are not yet used by the kernel to count such pages.
A later change adds
On Tue, 05 Oct 2010 00:33:15 -0700
Greg Thelen gthe...@google.com wrote:
KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com writes:
On Sun, 3 Oct 2010 23:58:03 -0700
Greg Thelen gthe...@google.com wrote:
Add cgroupfs interface to memcg dirty page limits:
Direct write-out is
On Tue, Oct 05, 2010 at 12:33:15AM -0700, Greg Thelen wrote:
KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com writes:
On Sun, 3 Oct 2010 23:58:03 -0700
Greg Thelen gthe...@google.com wrote:
Add cgroupfs interface to memcg dirty page limits:
Direct write-out is controlled with:
On Sun, Oct 03, 2010 at 11:58:02PM -0700, Greg Thelen wrote:
Extend mem_cgroup to contain dirty page limits. Also add routines
allowing the kernel to query the dirty usage of a memcg.
These interfaces not used by the kernel yet. A subsequent commit
will add kernel calls to utilize these
On Sun, Oct 03, 2010 at 11:57:58PM -0700, Greg Thelen wrote:
Replace usage of the mem_cgroup_update_file_mapped() memcg
statistic update routine with two new routines:
* mem_cgroup_inc_page_stat()
* mem_cgroup_dec_page_stat()
As before, only the file_mapped statistic is managed. However,
On Sun, Oct 03, 2010 at 11:57:59PM -0700, Greg Thelen wrote:
If pages are being migrated from a memcg, then updates to that
memcg's page statistics are protected by grabbing a bit spin lock
using lock_page_cgroup(). In an upcoming commit memcg dirty page
accounting will be updating memcg page
On Sun, Oct 03, 2010 at 11:58:00PM -0700, Greg Thelen wrote:
Add memcg routines to track dirty, writeback, and unstable_NFS pages.
These routines are not yet used by the kernel to count such pages.
A later change adds kernel calls to these new routines.
Signed-off-by: Greg Thelen
I resurect and refreshed this old patch from
https://lists.linux-foundation.org/pipermail/containers/2007-February/003726.html
This patch makes automount to work within a container.
Make autofs4 container-friendly by caching struct pid reference rather
than pid_t and using pid_nr() to retreive a
On Tue, 5 Oct 2010, Andrea Righi wrote:
mmh... looking at the code it seems the same behaviour, but in
Documentation/sysctl/vm.txt we say a different thing (i.e., for
dirty_bytes):
If dirty_bytes is written, dirty_ratio becomes a function of its value
(dirty_bytes / the amount of dirtyable
Andrea Righi ari...@develer.com writes:
On Sun, Oct 03, 2010 at 11:58:02PM -0700, Greg Thelen wrote:
Extend mem_cgroup to contain dirty page limits. Also add routines
allowing the kernel to query the dirty usage of a memcg.
These interfaces not used by the kernel yet. A subsequent commit
On Tue, 5 Oct 2010 12:38:05 +0400
Evgeny Kuznetsov ext-eugeny.kuznet...@nokia.com wrote:
From: Evgeny Kuznetsov ext-eugeny.kuznet...@nokia.com
Function strcpy is used without check for maximum allowed source
string length and could cause destination string overflow.
Check for string length
On Tue, Oct 5, 2010 at 12:48 PM, Andrew Morton
a...@linux-foundation.org wrote:
On Tue, 5 Oct 2010 12:38:05 +0400
Evgeny Kuznetsov ext-eugeny.kuznet...@nokia.com wrote:
From: Evgeny Kuznetsov ext-eugeny.kuznet...@nokia.com
Function strcpy is used without check for maximum allowed source
Minchan Kim minchan@gmail.com writes:
On Sun, Oct 03, 2010 at 11:57:58PM -0700, Greg Thelen wrote:
Replace usage of the mem_cgroup_update_file_mapped() memcg
statistic update routine with two new routines:
* mem_cgroup_inc_page_stat()
* mem_cgroup_dec_page_stat()
As before, only the
On Sun, Oct 03, 2010 at 11:57:55PM -0700, Greg Thelen wrote:
This patch set provides the ability for each cgroup to have independent dirty
page limits.
Limiting dirty memory is like fixing the max amount of dirty (hard to reclaim)
page cache used by a cgroup. So, in case of multiple cgroup
Minchan Kim minchan@gmail.com writes:
On Sun, Oct 03, 2010 at 11:57:59PM -0700, Greg Thelen wrote:
If pages are being migrated from a memcg, then updates to that
memcg's page statistics are protected by grabbing a bit spin lock
using lock_page_cgroup(). In an upcoming commit memcg dirty
On Wed, Oct 6, 2010 at 4:59 AM, Greg Thelen gthe...@google.com wrote:
Minchan Kim minchan@gmail.com writes:
On Sun, Oct 03, 2010 at 11:57:58PM -0700, Greg Thelen wrote:
Replace usage of the mem_cgroup_update_file_mapped() memcg
statistic update routine with two new routines:
*
On Wed, Oct 6, 2010 at 8:26 AM, Greg Thelen gthe...@google.com wrote:
Minchan Kim minchan@gmail.com writes:
On Sun, Oct 03, 2010 at 11:57:59PM -0700, Greg Thelen wrote:
If pages are being migrated from a memcg, then updates to that
memcg's page statistics are protected by grabbing a bit
On Mon, Oct 4, 2010 at 3:58 PM, Greg Thelen gthe...@google.com wrote:
If the current process is in a non-root memcg, then
global_dirty_limits() will consider the memcg dirty limit.
This allows different cgroups to have distinct dirty limits
which trigger direct and background writeback at
On Sun, 3 Oct 2010 23:57:56 -0700
Greg Thelen gthe...@google.com wrote:
Add additional flags to page_cgroup to track dirty pages
within a mem_cgroup.
Signed-off-by: KAMEZAWA Hiroyuki kamezawa.hir...@jp.fujitsu.com
Signed-off-by: Andrea Righi ari...@develer.com
Signed-off-by: Greg Thelen
On Sun, 3 Oct 2010 23:57:57 -0700
Greg Thelen gthe...@google.com wrote:
Document cgroup dirty memory interfaces and statistics.
Signed-off-by: Andrea Righi ari...@develer.com
Signed-off-by: Greg Thelen gthe...@google.com
I think you will change nfs to nfs_unstable, but anyway,
Acked-by:
* Greg Thelen gthe...@google.com [2010-10-03 23:57:55]:
This patch set provides the ability for each cgroup to have independent dirty
page limits.
Limiting dirty memory is like fixing the max amount of dirty (hard to reclaim)
page cache used by a cgroup. So, in case of multiple cgroup
Greg Kurz [gk...@fr.ibm.com] wrote:
| On Tue, 2010-09-07 at 13:03 -0700, Sukadev Bhattiprolu wrote:
| Suppose we create a container and redirect its stdout/stderr as follows:
|
| lxc-execute -name foo -- /path/to/app /tmp/xyz.out 21
|
| If we attempt to checkpoint the container 'foo',
35 matches
Mail list logo
