2016: Requests to attend MM-summit
Hi,
I would like to attend LSF/MM this year (2016).
My main interest is in MM related topics although I am also interested in the btrfs status discussion (particularly related to subpage size block size topic), if we are having one. Most of my recent work in the kernel is related to adding ppc64 support for different MM features. My current focus is on adding Linux support for the new radix MMU model of Power9.
Topics of interest include:
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not consider free_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with his ZOME_CMA patches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)
Others needed for the discussion:
Joonsoo Kim <[email protected]>
(2) CMA allocation failures due to pinned pages in the region:
We allow only movable allocation from the CMA region to enable us
to migrate those pages later when we get a CMA allocation request. But if we pin those movable pages, we will fail the migration which can result in CMA allocation failure. One such report can be found here.
http://article.gmane.org/gmane.linux.kernel.mm/136738
Peter Zijlstra's VM_PINNED patch series should help in fixing the issue. I would like to discuss what needs to be done to get this patch series merged upstream
https://lkml.org/lkml/2014/5/26/345 (VM_PINNED)
Others needed for the discussion:
Peter Zijlstra <[email protected]>
* Improvements to tlb flush
Archiectures like ppc64 can do range based tlb flush and for that we need
to know the page size used to map the virtual address range. I would like to discuss changes to mmu gather and tlb flush api that will help in efficient implementation of tlb flush for ppc64.
(1) MMU gather improvements
https://github.com/kvaneesh/linux/commit/215b9c7c03bb8d742349e2aefaadcf8cc0c04dd8 https://github.com/kvaneesh/linux/commit/43bd9e91a841bbc9e3c6ee56a4d12ed00019718c (2) different APIs to flush hugepage tlb mappings. https://github.com/kvaneesh/linux/commit/b8a78933fea93cb0b2978868e59a0a4b12eb92eb https://github.com/kvaneesh/linux/commit/049d361a59a3342c2ce5a4feae61dce4974af226
NOTE: I haven't posted these changes yet to the list because of dependent patches getting reviewed. But should have them available on the list before LSF/MM.
* HMM status (Heterogeneous Memory Management)
I would like to discuss the roadblocks w.r.t merging HMM patchset upstream.
http://article.gmane.org/gmane.linux.kernel.mm/140229
Others needed for the discussion:
Jérôme Glisse <[email protected]>
-aneesh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 31 lines · On Fri, 22 Jan 2016 10:11:12 +0530 "Aneesh Kumar K.V"…
Hi,
I would like to attend LSF/MM this year (2016).
My main interest is in MM related topics although I am also interested in the btrfs status discussion (particularly related to subpage size block size topic), if we are having one. Most of my recent work in the kernel is related to adding ppc64 support for different MM features. My current focus is on adding Linux support for the new radix MMU model of Power9.
Topics of interest include:
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)Others needed for the discussion:
Joonsoo Kim <[email protected]>(2) CMA allocation failures due to pinned pages in the region:
We allow only movable allocation from the CMA region to enable us
to migrate those pages later when we get a CMA allocation request. But if we pin those movable pages, we will fail the migration which can result in CMA allocation failure. One such report can be found here.
http://article.gmane.org/gmane.linux.kernel.mm/136738
Quoted 6 lines
Peter Zijlstra's
VM_PINNEDpatch series should help in fixing the issue. I would like to discuss what needs to be done to get this patch series merged upstream
https://lkml.org/lkml/2014/5/26/345 (VM_PINNED)Others needed for the discussion:
Peter Zijlstra <[email protected]>
+1
I agree CMA design is a concern. I also noticed that today all CMA pages come from one node. On a NUMA box you'll see cross traffic going to that region - although from kernel only text. It should be discussed at the summit and Aneesh would be a good representative
Balbir Singh.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 41 lines · Balbir Singh
Quoted 31 lines · On Fri, 22 Jan 2016 10:11:12 +0530 "Aneesh Kumar K.V"…
Hi,
I would like to attend LSF/MM this year (2016).
My main interest is in MM related topics although I am also interested in the btrfs status discussion (particularly related to subpage size block size topic), if we are having one. Most of my recent work in the kernel is related to adding ppc64 support for different MM features. My current focus is on adding Linux support for the new radix MMU model of Power9.
Topics of interest include:
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)Others needed for the discussion:
Joonsoo Kim <[email protected]>(2) CMA allocation failures due to pinned pages in the region:
We allow only movable allocation from the CMA region to enable us
to migrate those pages later when we get a CMA allocation request. But if we pin those movable pages, we will fail the migration which can result in CMA allocation failure. One such report can be found here.
http://article.gmane.org/gmane.linux.kernel.mm/136738Quoted 6 lines
Peter Zijlstra's
VM_PINNEDpatch series should help in fixing the issue. I would like to discuss what needs to be done to get this patch series merged upstream
https://lkml.org/lkml/2014/5/26/345 (VM_PINNED)Others needed for the discussion:
Peter Zijlstra <[email protected]>
Quoted 6 lines
+1
I agree CMA design is a concern. I also noticed that today all CMA pages come from one node. On a NUMA box you'll see cross traffic going to that region - although from kernel only text. It should be discussed at the summit and Aneesh would be a good representative
I'm not really an mm guy but CMA has been discussed already last year, and I think even the year before... Are we moving somewhere? So if this is about hashing out what blocks VM_PINNED series (I think it may be just a lack of Peter's persistence in pushing it ;) then that looks like a sensible goal. Some other CMA architecture discussions need IMHO a more concrete proposals...
Honza
Signature · 8 lines
Jan Kara <[email protected]> SUSE Labs, CR -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 49 lines · Jan Kara
Quoted 41 lines · Balbir Singh
Quoted 31 lines · On Fri, 22 Jan 2016 10:11:12 +0530 "Aneesh Kumar K.V"…
Hi,
I would like to attend LSF/MM this year (2016).
My main interest is in MM related topics although I am also interested in the btrfs status discussion (particularly related to subpage size block size topic), if we are having one. Most of my recent work in the kernel is related to adding ppc64 support for different MM features. My current focus is on adding Linux support for the new radix MMU model of Power9.
Topics of interest include:
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)Others needed for the discussion:
Joonsoo Kim <[email protected]>(2) CMA allocation failures due to pinned pages in the region:
We allow only movable allocation from the CMA region to enable us
to migrate those pages later when we get a CMA allocation request. But if we pin those movable pages, we will fail the migration which can result in CMA allocation failure. One such report can be found here.
http://article.gmane.org/gmane.linux.kernel.mm/136738Quoted 6 lines
Peter Zijlstra's
VM_PINNEDpatch series should help in fixing the issue. I would like to discuss what needs to be done to get this patch series merged upstream
https://lkml.org/lkml/2014/5/26/345 (VM_PINNED)Others needed for the discussion:
Peter Zijlstra <[email protected]>Quoted 6 lines
+1
I agree CMA design is a concern. I also noticed that today all CMA pages come from one node. On a NUMA box you'll see cross traffic going to that region - although from kernel only text. It should be discussed at the summit and Aneesh would be a good representative
Quoted 9 lines
I'm not really an mm guy but CMA has been discussed already last year, and I think even the year before... Are we moving somewhere? So if this is about hashing out what blocks
VM_PINNEDseries (I think it may be just a lack of Peter's persistence in pushing it ;) then that looks like a sensible goal. Some other CMA architecture discussions need IMHO a more concrete proposals...Honza
The conclusion from the CMA session last year was that pinned pages need to be fixed up at the caller sites doing the pinning. Each caller site really needs to be taken individually. I think the discussion last year was good but if it's going to end up with a different conclusion I agree there needs to be concrete proposals.
Something that could be worth discussing as well is Joonsoo Kim's proposal for page reference tracking http://thread.gmane.org/gmane.linux.kernel.api/16138
Thanks,
Laura
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 23 lines · Laura Abbott
Quoted 12 lines · Jan Kara
Quoted 10 lines · Balbir Singh
On Fri, 22 Jan 2016 10:11:12 +0530
"Aneesh Kumar K.V" <[email protected]> wrote:+1
I agree CMA design is a concern. I also noticed that today all CMA pages come from one node. On a NUMA box you'll see cross traffic going to that region - although from kernel only text. It should be discussed at the summit and Aneesh would be a good representative
Quoted 9 lines
I'm not really an mm guy but CMA has been discussed already last year, and I think even the year before... Are we moving somewhere? So if this is about hashing out what blocks
VM_PINNEDseries (I think it may be just a lack of Peter's persistence in pushing it ;) then that looks like a sensible goal. Some other CMA architecture discussions need IMHO a more concrete proposals...Honza
Quoted 8 lines
The conclusion from the CMA session last year was that pinned pages need to be fixed up at the caller sites doing the pinning. Each caller site really needs to be taken individually. I think the discussion last year was good but if it's going to end up with a different conclusion I agree there needs to be concrete proposals.
Something that could be worth discussing as well is Joonsoo Kim's proposal for page reference tracking http://thread.gmane.org/gmane.linux.kernel.api/16138
I think indentifying the pinners and actually doing something about them, are different things. The tracking might help with the identification. Maybe some pins can be removed as found to be unneeded, but VM_PINNED infrastructure should help with dealing with the genuine ones - IIRC the idea was that prior to (relatively long-term) pinning, the pages would be migrated away from MOVABLE or CMA pageblocks to reduce fragmentation/allow CMA allocations succeed. Otherwise the only other option I see for genuine long-term pins is to pre-emptively allocate such pages as UNMOVABLE. A waste in case it's a large class of pages where only a subset of them (not known upfront) is going to be pinned. What if the class is e.g. "userspace-mapped pages"?
Quoted 9 lines
Thanks,
Laura--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 57 lines · Laura Abbott
Quoted 56 lines · Jan Kara
Quoted 41 lines · Balbir Singh
Quoted 31 lines · On Fri, 22 Jan 2016 10:11:12 +0530 "Aneesh Kumar K.V"…
Hi,
I would like to attend LSF/MM this year (2016).
My main interest is in MM related topics although I am also interested in the btrfs status discussion (particularly related to subpage size block size topic), if we are having one. Most of my recent work in the kernel is related to adding ppc64 support for different MM features. My current focus is on adding Linux support for the new radix MMU model of Power9.
Topics of interest include:
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)Others needed for the discussion:
Joonsoo Kim <[email protected]>(2) CMA allocation failures due to pinned pages in the region:
We allow only movable allocation from the CMA region to enable us
to migrate those pages later when we get a CMA allocation request. But if we pin those movable pages, we will fail the migration which can result in CMA allocation failure. One such report can be found here.
http://article.gmane.org/gmane.linux.kernel.mm/136738Quoted 6 lines
Peter Zijlstra's
VM_PINNEDpatch series should help in fixing the issue. I would like to discuss what needs to be done to get this patch series merged upstream
https://lkml.org/lkml/2014/5/26/345 (VM_PINNED)Others needed for the discussion:
Peter Zijlstra <[email protected]>Quoted 6 lines
+1
I agree CMA design is a concern. I also noticed that today all CMA pages come from one node. On a NUMA box you'll see cross traffic going to that region - although from kernel only text. It should be discussed at the summit and Aneesh would be a good representative
I'm not really an mm guy but CMA has been discussed already last year, and I think even the year before... Are we moving somewhere? So if this is about hashing out what blocks
VM_PINNEDseries (I think it may be just a lack of Peter's persistence in pushing it ;) then that looks like a sensible goal. Some other CMA architecture discussions need IMHO a more concrete proposals...
Quoted 8 lines
Quoted 2 lines
Honza
The conclusion from the CMA session last year was that pinned pages need to be fixed up at the caller sites doing the pinning. Each caller site really needs to be taken individually. I think the discussion last year was good but if it's going to end up with a different conclusion I agree there needs to be concrete proposals.
But that was not what was suggested in the kvm guest ram pin due to vfio thread I linked above. I think we still need to have an agreement on whether the callers should be migrating the pages or a generic framework like VM_PINNED is needed.
Quoted 6 lines
Something that could be worth discussing as well is Joonsoo Kim's proposal for page reference tracking http://thread.gmane.org/gmane.linux.kernel.api/16138
Thanks,
Laura
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Hi,
Quoted 8 lines · Aneesh Kumar K.V
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)
The exclusion of cma pages from the watermark checks means that reclaim is happening too early, not too late, which leaves memory underutilized. That's what ZONE_CMA set out to fix.
But unmovable allocations can still fail when the only free memory is inside CMA regions. I don't see how ZONE_CMA would fix that.
CC Joonsoo
But as Jan said, we discussed ZONE_CMA before, so it's not clear whether rehashing it without new data points would be too useful.
Quoted 10 lines
Others needed for the discussion:
Joonsoo Kim <[email protected]>(2) CMA allocation failures due to pinned pages in the region:
We allow only movable allocation from the CMA region to enable us
to migrate those pages later when we get a CMA allocation request. But if we pin those movable pages, we will fail the migration which can result in CMA allocation failure. One such report can be found here.
http://article.gmane.org/gmane.linux.kernel.mm/136738
Quoted 6 lines
Peter Zijlstra's
VM_PINNEDpatch series should help in fixing the issue. I would like to discuss what needs to be done to get this patch series merged upstream
https://lkml.org/lkml/2014/5/26/345 (VM_PINNED)Others needed for the discussion:
Peter Zijlstra <[email protected]>
There was no consensus whether this specific implementation would work well for all sources of pinning. Giving this some time in the MM track could be useful.
CC Peter
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Hello,
2016-01-23 1:38 GMT+09:00 Johannes Weiner <[email protected]>:
Quoted 11 lines
Hi,
Quoted 8 lines · Aneesh Kumar K.V
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)
As far as I know, there is no disagreement on this patchset in last year LSF/MM. Problem may be due to my laziness... Sorry about that. I will handle it soon. Is there anything more that you concern?
Quoted 8 lines
The exclusion of cma pages from the watermark checks means that reclaim is happening too early, not too late, which leaves memory underutilized. That's what
ZONE_CMAset out to fix.But unmovable allocations can still fail when the only free memory is inside CMA regions. I don't see how
ZONE_CMAwould fix that.CC Joonsoo
I understand what Aneesh's problem is.
Assume that
X = non movable free page
Y = movable free page
Z = cma free page
X < min watermark
X + Y > high watermark
Z > high watermark
If there are bunch of consecutive movable allocation requests, Y will decrease. After some time, Y will be exhausted. At that time, there is enough Z so movable allocation request still can be handled in fastpath and kswapd isn't waked up. In that situation, if atomic non-movable page allocation for order-0 comes, it would be failed.
Although it isn't mentioned on ZONE_CMA patchset, it is also fixed by that patchset because with that patchset, all CMA pages are in CMA zone so freepage calculation is always precise.
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 15 lines · Joonsoo Kim
Hello,
2016-01-23 1:38 GMT+09:00 Johannes Weiner <[email protected]>:
Quoted 11 lines
Hi,
Quoted 8 lines · Aneesh Kumar K.V
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)
Quoted 4 lines
As far as I know, there is no disagreement on this patchset in last year LSF/MM. Problem may be due to my laziness... Sorry about that. I will handle it soon. Is there anything more that you concern?
Is that series going to conflict with the work done for ZONE_DEVICE or run into similar problems?033fbae988fcb67e5077203512181890848b8e90 (mm: ZONE_DEVICE for "device memory") has commit text about running out of ZONE_SHIFT bits and needing to get rid of ZONE_DMA instead so it seems like ZONE_CMA would run into the same problem.
Thanks,
Laura
Quoted 32 lines
Quoted 8 lines
The exclusion of cma pages from the watermark checks means that reclaim is happening too early, not too late, which leaves memory underutilized. That's what
ZONE_CMAset out to fix.But unmovable allocations can still fail when the only free memory is inside CMA regions. I don't see how
ZONE_CMAwould fix that.CC Joonsoo
I understand what Aneesh's problem is.
Assume that
X = non movable free page
Y = movable free page
Z = cma free pageX < min watermark
X + Y > high watermark
Z > high watermarkIf there are bunch of consecutive movable allocation requests, Y will decrease. After some time, Y will be exhausted. At that time, there is enough Z so movable allocation request still can be handled in fastpath and kswapd isn't waked up. In that situation, if atomic non-movable page allocation for order-0 comes, it would be failed.
Although it isn't mentioned on
ZONE_CMApatchset, it is also fixed by that patchset because with that patchset, all CMA pages are in CMA zone so freepage calculation is always precise.
Quoted 8 lines
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 21 lines · Laura Abbott
Quoted 15 lines · Joonsoo Kim
Hello,
2016-01-23 1:38 GMT+09:00 Johannes Weiner <[email protected]>:
Quoted 11 lines
Hi,
Quoted 8 lines · Aneesh Kumar K.V
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)Quoted 4 lines
As far as I know, there is no disagreement on this patchset in last year LSF/MM. Problem may be due to my laziness... Sorry about that. I will handle it soon. Is there anything more that you concern?
Quoted 6 lines
Is that series going to conflict with the work done for
ZONE_DEVICEor run into similar problems?033fbae988fcb67e5077203512181890848b8e90(mm:ZONE_DEVICEfor "device memory") has commit text about running out ofZONE_SHIFTbits and needing to get rid ofZONE_DMAinstead so it seems likeZONE_CMAwould run into the same problem.
Hmm... I'm not sure. I need a investigation. What I did before is enlarging section size. Then, number of section is reduced and we need less section bit in struct page's flag. This worked for my sparsemem configuration but I'm not sure other conguration. Perhaps, in other congifuration, we can limit node bits and max number of node.
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 9 lines · Joonsoo Kim
Quoted 7 lines · Laura Abbott
Is that series going to conflict with the work done for
ZONE_DEVICEor run into similar problems?033fbae988fcb67e5077203512181890848b8e90(mm:ZONE_DEVICEfor "device memory") has commit text about running out ofZONE_SHIFTbits and needing to get rid ofZONE_DMAinstead so it seems likeZONE_CMAwould run into the same problem.
Quoted 5 lines
Hmm... I'm not sure. I need a investigation. What I did before is enlarging section size. Then, number of section is reduced and we need less section bit in struct page's flag. This worked for my sparsemem configuration but I'm not sure other conguration. Perhaps, in other congifuration, we can limit node bits and max number of node.
This seems to be a solution proposed for the ZONE_DMA and ZONE_DEVICE coexistence https://lkml.org/lkml/2016/1/25/1233
It wouldn't help with ZONE_CMA, so I guess it's time to look for a more robust one.
Quoted 8 lines
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 47 lines · Joonsoo Kim
Hello,
2016-01-23 1:38 GMT+09:00 Johannes Weiner <[email protected]>:
Quoted 11 lines
Hi,
Quoted 8 lines · Aneesh Kumar K.V
* CMA allocator issues:
(1) order zero allocation failures:
We are observing order zero non-movable allocation failures in kernel
with CMA configured. We don't start a reclaim because our free memory check does not considerfree_cma. Hence the reclaim code assume we have enough free pages. Joonsoo Kim tried to fix this with hisZOME_CMApatches. I would like to discuss the challenges in getting this merged upstream.
https://lkml.org/lkml/2015/2/12/95 (ZONE_CMA)As far as I know, there is no disagreement on this patchset in last year LSF/MM. Problem may be due to my laziness... Sorry about that. I will handle it soon. Is there anything more that you concern?
Quoted 8 lines
The exclusion of cma pages from the watermark checks means that reclaim is happening too early, not too late, which leaves memory underutilized. That's what
ZONE_CMAset out to fix.But unmovable allocations can still fail when the only free memory is inside CMA regions. I don't see how
ZONE_CMAwould fix that.CC Joonsoo
I understand what Aneesh's problem is.
Assume that
X = non movable free page
Y = movable free page
Z = cma free pageX < min watermark
X + Y > high watermark
Z > high watermarkIf there are bunch of consecutive movable allocation requests, Y will decrease. After some time, Y will be exhausted. At that time, there is enough Z so movable allocation request still can be handled in fastpath and kswapd isn't waked up. In that situation, if atomic non-movable page allocation for order-0 comes, it would be failed.
Quoted 4 lines
Although it isn't mentioned on
ZONE_CMApatchset, it is also fixed by that patchset because with that patchset, all CMA pages are in CMA zone so freepage calculation is always precise.
That is the issue I am hitting and if we don't have any blocker against ZONE_CMA then we can drop this topic.
-aneesh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 11 lines · Johannes Weiner
Quoted 7 lines
Peter Zijlstra's
VM_PINNEDpatch series should help in fixing the issue. I would like to discuss what needs to be done to get this patch series merged upstream
https://lkml.org/lkml/2014/5/26/345 (VM_PINNED)Others needed for the discussion:
Peter Zijlstra <[email protected]>There was no consensus whether this specific implementation would work well for all sources of pinning. Giving this some time in the MM track could be useful.
I got stuck and lost in IB land. But that was a fair while ago. I should probably look at rebasing it against something recent, although I seriuosly doubt I can get through IB this time.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>