Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-26 Thread Bruce Merry
On 24 July 2018 at 12:05, Bruce Merry wrote: > To reproduce: > 1. Start cadvisor running. I use the 0.30.2 binary from Github, and > run it with sudo ./cadvisor-0.30.2 --logtostderr=true > 2. Run the Python 3 script below, which repeatedly creates a cgroup, > enters it, s

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-26 Thread Bruce Merry
On 24 July 2018 at 12:05, Bruce Merry wrote: > To reproduce: > 1. Start cadvisor running. I use the 0.30.2 binary from Github, and > run it with sudo ./cadvisor-0.30.2 --logtostderr=true > 2. Run the Python 3 script below, which repeatedly creates a cgroup, > enters it, s

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-26 Thread Bruce Merry
Bruce -- Bruce Merry Senior Science Processing Developer SKA South Africa

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-26 Thread Bruce Merry
Bruce -- Bruce Merry Senior Science Processing Developer SKA South Africa

Re: [PATCH] memcg: reduce memcg tree traversals for stats collection

2018-07-25 Thread Bruce Merry
changed at around 18ms (was 20ms, but there were slightly more cgroups as well), compared to the almost 4x speedup you're seeing in your test. Regards Bruce -- Bruce Merry Senior Science Processing Developer SKA South Africa

Re: [PATCH] memcg: reduce memcg tree traversals for stats collection

2018-07-25 Thread Bruce Merry
changed at around 18ms (was 20ms, but there were slightly more cgroups as well), compared to the almost 4x speedup you're seeing in your test. Regards Bruce -- Bruce Merry Senior Science Processing Developer SKA South Africa

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-24 Thread Bruce Merry
On 18 July 2018 at 19:40, Bruce Merry wrote: >> Yes, very easy to produce zombies, though I don't think kernel >> provides any way to tell how many zombies exist on the system. >> >> To create a zombie, first create a memcg node, enter that memcg, >> create

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-24 Thread Bruce Merry
On 18 July 2018 at 19:40, Bruce Merry wrote: >> Yes, very easy to produce zombies, though I don't think kernel >> provides any way to tell how many zombies exist on the system. >> >> To create a zombie, first create a memcg node, enter that memcg, >> create

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 20:13, Shakeel Butt wrote: > On Wed, Jul 18, 2018 at 10:58 AM Bruce Merry wrote: > Yes, if there is no memory pressure such memory can stay around. > > On your production machine, before deleting memory containers, you can > try force_empty to reclaim such m

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 20:13, Shakeel Butt wrote: > On Wed, Jul 18, 2018 at 10:58 AM Bruce Merry wrote: > Yes, if there is no memory pressure such memory can stay around. > > On your production machine, before deleting memory containers, you can > try force_empty to reclaim such m

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 19:48, Shakeel Butt wrote: > On Wed, Jul 18, 2018 at 10:40 AM Bruce Merry wrote: >> > Yes, very easy to produce zombies, though I don't think kernel >> > provides any way to tell how many zombies exist on the system. >> > >> > To cre

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 19:48, Shakeel Butt wrote: > On Wed, Jul 18, 2018 at 10:40 AM Bruce Merry wrote: >> > Yes, very easy to produce zombies, though I don't think kernel >> > provides any way to tell how many zombies exist on the system. >> > >> > To cre

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 17:49, Shakeel Butt wrote: > On Wed, Jul 18, 2018 at 8:37 AM Bruce Merry wrote: >> That sounds promising. Is there any way to tell how many zombies there >> are, and is there any way to deliberately create zombies? If I can >> produce zombies that might g

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 17:49, Shakeel Butt wrote: > On Wed, Jul 18, 2018 at 8:37 AM Bruce Merry wrote: >> That sounds promising. Is there any way to tell how many zombies there >> are, and is there any way to deliberately create zombies? If I can >> produce zombies that might g

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 17:26, Shakeel Butt wrote: > On Wed, Jul 18, 2018 at 7:29 AM Bruce Merry wrote: > It seems like you are using cgroup-v1. How many nodes are there in > your memcg tree and also how many cpus does the system have? >From my original email: "there are 106

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 17:26, Shakeel Butt wrote: > On Wed, Jul 18, 2018 at 7:29 AM Bruce Merry wrote: > It seems like you are using cgroup-v1. How many nodes are there in > your memcg tree and also how many cpus does the system have? >From my original email: "there are 106

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
o the stat_show cost of its parent or does it have to have some non-trivial variation from its parent? Thanks Bruce -- Bruce Merry Senior Science Processing Developer SKA South Africa

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
o the stat_show cost of its parent or does it have to have some non-trivial variation from its parent? Thanks Bruce -- Bruce Merry Senior Science Processing Developer SKA South Africa

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 12:42, Michal Hocko wrote: > [CC some more people] > > On Tue 17-07-18 21:23:07, Andrew Morton wrote: >> (cc linux-mm) >> >> On Tue, 3 Jul 2018 08:43:23 +0200 Bruce Merry wrote: >> >> > Hi >> > >> > I've ru

Re: Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-18 Thread Bruce Merry
On 18 July 2018 at 12:42, Michal Hocko wrote: > [CC some more people] > > On Tue 17-07-18 21:23:07, Andrew Morton wrote: >> (cc linux-mm) >> >> On Tue, 3 Jul 2018 08:43:23 +0200 Bruce Merry wrote: >> >> > Hi >> > >> > I've ru

Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-03 Thread Bruce Merry
ow to prevent it happening? Thanks Bruce -- Bruce Merry Senior Science Processing Developer SKA South Africa

Showing /sys/fs/cgroup/memory/memory.stat very slow on some machines

2018-07-03 Thread Bruce Merry
ow to prevent it happening? Thanks Bruce -- Bruce Merry Senior Science Processing Developer SKA South Africa

[tip:perf/urgent] perf bench: Fix order of arguments to memcpy_alloc_mem

2015-03-01 Thread tip-bot for Bruce Merry
Commit-ID: e17fdaeaec066c725f73cd3cda1feae52b2646f5 Gitweb: http://git.kernel.org/tip/e17fdaeaec066c725f73cd3cda1feae52b2646f5 Author: Bruce Merry AuthorDate: Thu, 15 Jan 2015 11:20:22 +0200 Committer: Arnaldo Carvalho de Melo CommitDate: Sun, 22 Feb 2015 23:10:56 -0300 perf bench

[tip:perf/urgent] perf bench: Fix order of arguments to memcpy_alloc_mem

2015-03-01 Thread tip-bot for Bruce Merry
Commit-ID: e17fdaeaec066c725f73cd3cda1feae52b2646f5 Gitweb: http://git.kernel.org/tip/e17fdaeaec066c725f73cd3cda1feae52b2646f5 Author: Bruce Merry bme...@ska.ac.za AuthorDate: Thu, 15 Jan 2015 11:20:22 +0200 Committer: Arnaldo Carvalho de Melo a...@redhat.com CommitDate: Sun, 22 Feb 2015

[PATCH v2] perf bench: fix order of arguments to memcpy_alloc_mem

2015-01-15 Thread Bruce Merry
This was causing the destination instead of the source to be filled. As a result, the source was typically all mapped to one zero page, and hence very cacheable. Signed-off-by: Bruce Merry --- tools/perf/bench/mem-memcpy.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] perf bench: fix order of arguments to memcpy_alloc_mem

2015-01-15 Thread Bruce Merry
len); if (prefault) fn(dst, src, len); -- 1.9.1 -- Bruce Merry Senior Science Processing Developer SKA South Africa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo

[PATCH] perf bench: fix order of arguments to memcpy_alloc_mem

2015-01-15 Thread Bruce Merry
); +memcpy_alloc_mem(dst, src, len); if (prefault) fn(dst, src, len); -- 1.9.1 -- Bruce Merry Senior Science Processing Developer SKA South Africa -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info

[PATCH v2] perf bench: fix order of arguments to memcpy_alloc_mem

2015-01-15 Thread Bruce Merry
This was causing the destination instead of the source to be filled. As a result, the source was typically all mapped to one zero page, and hence very cacheable. Signed-off-by: Bruce Merry bme...@ska.ac.za --- tools/perf/bench/mem-memcpy.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions

Oops error

2000-09-11 Thread Bruce Merry
and refused to die, even with kill -9. I'm guessing that this means the problem is in either the CD-ROM code or the UDF code, but it might be unrelated. I've attached the output from ksymoops. B4N Bruce /\ | Bruce Merry (Entropy

Oops error

2000-09-11 Thread Bruce Merry
and refused to die, even with kill -9. I'm guessing that this means the problem is in either the CD-ROM code or the UDF code, but it might be unrelated. I've attached the output from ksymoops. B4N Bruce /\ | Bruce Merry (Entropy