Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Michal Hocko
On Mon 02-10-17 13:24:25, Shakeel Butt wrote: > On Mon, Oct 2, 2017 at 12:56 PM, Michal Hocko wrote: > > On Mon 02-10-17 12:45:18, Shakeel Butt wrote: > >> > I am sorry to cut the rest of your proposal because it simply goes over > >> > the scope of the proposed solution while

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Shakeel Butt
On Mon, Oct 2, 2017 at 12:56 PM, Michal Hocko wrote: > On Mon 02-10-17 12:45:18, Shakeel Butt wrote: >> > I am sorry to cut the rest of your proposal because it simply goes over >> > the scope of the proposed solution while the usecase you are mentioning >> > is still possible.

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Johannes Weiner
On Mon, Oct 02, 2017 at 01:24:25PM -0700, Shakeel Butt wrote: > On Mon, Oct 2, 2017 at 12:56 PM, Michal Hocko wrote: > > On Mon 02-10-17 12:45:18, Shakeel Butt wrote: > >> > I am sorry to cut the rest of your proposal because it simply goes over > >> > the scope of the proposed

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Tim Hockin
In the example above: root /\ A D / \ B C Does oom_group allow me to express "compare A and D; if A is chosen compare B and C; kill the loser" ? As I understand the proposal (from reading thread, not patch) it does not. On Mon, Oct 2, 2017 at 12:56 PM,

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Michal Hocko
On Mon 02-10-17 13:00:54, Tim Hockin wrote: > In the example above: > >root >/\ > A D > / \ >B C > > Does oom_group allow me to express "compare A and D; if A is chosen > compare B and C; kill the loser" ? As I understand the proposal (from > reading

[PATCH] doc: dev-tools: kselftest.rst: update to include make O=dir support

2017-10-02 Thread Shuah Khan
Update to include details on make O=dir support and other changes improve test results output. Signed-off-by: Shuah Khan --- Documentation/dev-tools/kselftest.rst | 34 -- 1 file changed, 32 insertions(+), 2 deletions(-) diff --git

[PATCH] doc: enhance dochelp include default output location for doc build

2017-10-02 Thread Shuah Khan
Enhance documentation help message to specify the default location for the generated documents. Signed-off-by: Shuah Khan --- Documentation/Makefile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/Makefile b/Documentation/Makefile index

Re: [PATCH] mm,hugetlb,migration: don't migrate kernelcore hugepages

2017-10-02 Thread Alexandru Moise
On Mon, Oct 02, 2017 at 06:15:00PM +0200, Michal Hocko wrote: > On Mon 02-10-17 17:06:38, Alexandru Moise wrote: > > On Mon, Oct 02, 2017 at 04:27:17PM +0200, Michal Hocko wrote: > > > On Mon 02-10-17 16:06:33, Alexandru Moise wrote: > > > > On Mon, Oct 02, 2017 at 02:54:32PM +0200, Michal Hocko

Re: [PATCH] mm,hugetlb,migration: don't migrate kernelcore hugepages

2017-10-02 Thread Alexandru Moise
On Mon, Oct 02, 2017 at 02:54:32PM +0200, Michal Hocko wrote: > On Mon 02-10-17 00:51:11, Alexandru Moise wrote: > > This attempts to bring more flexibility to how hugepages are allocated > > by making it possible to decide whether we want the hugepages to be > > allocated from ZONE_MOVABLE or to

Re: [PATCH] mm,hugetlb,migration: don't migrate kernelcore hugepages

2017-10-02 Thread Michal Hocko
On Mon 02-10-17 16:06:33, Alexandru Moise wrote: > On Mon, Oct 02, 2017 at 02:54:32PM +0200, Michal Hocko wrote: > > On Mon 02-10-17 00:51:11, Alexandru Moise wrote: > > > This attempts to bring more flexibility to how hugepages are allocated > > > by making it possible to decide whether we want

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Michal Hocko
On Mon 02-10-17 13:47:12, Roman Gushchin wrote: > On Mon, Oct 02, 2017 at 02:24:34PM +0200, Michal Hocko wrote: [...] > > I believe the latest version (v9) looks sensible from the semantic point > > of view and we should focus on making it into a mergeable shape. > > The only thing is that after

Re: [PATCH] mm,hugetlb,migration: don't migrate kernelcore hugepages

2017-10-02 Thread Michal Hocko
On Mon 02-10-17 00:51:11, Alexandru Moise wrote: > This attempts to bring more flexibility to how hugepages are allocated > by making it possible to decide whether we want the hugepages to be > allocated from ZONE_MOVABLE or to the zone allocated by the "kernelcore=" > boot parameter for

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Roman Gushchin
On Mon, Oct 02, 2017 at 02:24:34PM +0200, Michal Hocko wrote: > On Sun 01-10-17 16:29:48, Shakeel Butt wrote: > > > > > > Going back to Michal's example, say the user configured the following: > > > > > >root > > > /\ > > > A D > > > / \ > > >B C > > > > > > A

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Tetsuo Handa
Shakeel Butt wrote: > I think Tim has given very clear explanation why comparing A & D makes > perfect sense. However I think the above example, a single user system > where a user has designed and created the whole hierarchy and then > attaches different jobs/applications to different nodes in

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Michal Hocko
On Sun 01-10-17 16:29:48, Shakeel Butt wrote: > > > > Going back to Michal's example, say the user configured the following: > > > >root > > /\ > > A D > > / \ > >B C > > > > A global OOM event happens and we find this: > > - A > D > > - B, C, D are oomgroups

Re: [PATCH] mm,hugetlb,migration: don't migrate kernelcore hugepages

2017-10-02 Thread Alexandru Moise
On Mon, Oct 02, 2017 at 04:27:17PM +0200, Michal Hocko wrote: > On Mon 02-10-17 16:06:33, Alexandru Moise wrote: > > On Mon, Oct 02, 2017 at 02:54:32PM +0200, Michal Hocko wrote: > > > On Mon 02-10-17 00:51:11, Alexandru Moise wrote: > > > > This attempts to bring more flexibility to how hugepages

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Shakeel Butt
> Yes and nobody is disputing that, really. I guess the main disconnect > here is that different people want to have more detailed control over > the victim selection while the patchset tries to handle the most > simplistic scenario when a no userspace control over the selection is > required. And

Re: [PATCH] mm,hugetlb,migration: don't migrate kernelcore hugepages

2017-10-02 Thread Michal Hocko
On Mon 02-10-17 17:06:38, Alexandru Moise wrote: > On Mon, Oct 02, 2017 at 04:27:17PM +0200, Michal Hocko wrote: > > On Mon 02-10-17 16:06:33, Alexandru Moise wrote: > > > On Mon, Oct 02, 2017 at 02:54:32PM +0200, Michal Hocko wrote: > > > > On Mon 02-10-17 00:51:11, Alexandru Moise wrote: > > > >

Re: [PATCH v3] doc: coresight: correct usage for disabling idle states

2017-10-02 Thread Mathieu Poirier
On 19 September 2017 at 21:46, Leo Yan wrote: > In the coresight CPU debug document it suggests to use 'echo' command > to set latency request to /dev/cpu_dma_latency so can disable all CPU > idle states, but in fact this doesn't work. > > This is because when the command

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Michal Hocko
On Mon 02-10-17 12:00:43, Shakeel Butt wrote: > > Yes and nobody is disputing that, really. I guess the main disconnect > > here is that different people want to have more detailed control over > > the victim selection while the patchset tries to handle the most > > simplistic scenario when a no

Re: [v8 0/4] cgroup-aware OOM killer

2017-10-02 Thread Shakeel Butt
> I am sorry to cut the rest of your proposal because it simply goes over > the scope of the proposed solution while the usecase you are mentioning > is still possible. If we want to compare intermediate nodes (which seems > to be the case) then we can always provide a knob to opt-in - be it your