Add a new scheme to support demotion on tiered memory system
Subsystems (5)
Baolin Wang
reviewerv2 cover Add a new scheme to support demotion on tiered memory system
Hi,
Now on tiered memory system with different memory types, the reclaim path in shrink_page_list() already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.
We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
This patch set introduces a new scheme named DAMOS_DEMOTE to support this feature, and works well from my testing. Any comments are welcome. Thanks.
Changes from v1:
- Reuse the demote_page_list().
- Fix some comments style issues.
- Move the DAMOS_DEMOTE definition to the correct place.
- Rename some function name.
- Change to return void type for damos_isolate_page().
- Remove unnecessary PAGE_ALIGN() in damos_demote().
- Fix the return value for damos_demote().
Baolin Wang (2):
mm: Export the demote_page_list() function
mm/damon: Add a new scheme to support demotion on tiered memory system
include/linux/damon.h | 3 ++ mm/damon/dbgfs.c | 1 + mm/damon/vaddr.c | 147 ++++++++++++++++++++++++++++++++++++++++++++++++++ mm/internal.h | 2 + mm/vmscan.c | 4 +- 5 files changed, 155 insertions(+), 2 deletions(-)
Signature · 1 line
1.8.3.1
Baolin Wang
reviewerPATCH v2 1/2 mm: Export the demote_page_list() function
Export the demote_page_list() function to the head file as a preparation to support page demotion for DAMON monitor.
--- mm/internal.h | 2 ++ mm/vmscan.c | 4 ++-- 2 files changed, 4 insertions(+), 2 deletions(-)
mm/internal.h +2 -0
@@ -181,6 +181,8 @@ static inline void set_page_refcounted(struct page *page)extern int isolate_lru_page (struct page *page);extern void putback_lru_page (struct page *page);extern void reclaim_throttle (pg_data_t *pgdat,enum vmscan_throttle_state reason); +extern unsigned int demote_page_list (struct list_head *demote_pages, +struct pglist_data *pgdat);/* * in mm/rmap.c:
mm/vmscan.c +2 -2
@@ -1480,8 +1480,8 @@ static struct page *alloc_demote_page(struct page *page, unsigned long node)* another node. Pages which are not demoted are left on * @demote_pages. */ -static unsigned int demote_page_list (struct list_head *demote_pages, -struct pglist_data *pgdat) +unsigned int demote_page_list (struct list_head *demote_pages, +struct pglist_data *pgdat) {int target_nid =next_demotion_node (pgdat->node_id);unsigned int nr_succeeded;
Signature · 1 line
1.8.3.1
Baolin Wang
reviewerPATCH v2 2/2 mm/damon: Add a new scheme to support demotion on tiered memory system
In reply to Baolin WangOn tiered memory system, the reclaim path in shrink_page_list() already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion.
We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state. Thus this patch introduces a new scheme named DAMOS_DEMOTE to support this feature.
--- include/linux/damon.h | 3 ++ mm/damon/dbgfs.c | 1 + mm/damon/vaddr.c | 147 ++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 151 insertions(+)
include/linux/damon.h +3 -0
@@ -87,6 +87,8 @@ struct damon_target {* @DAMOS_PAGEOUT: Call ``madvise()`` for the region with MADV_PAGEOUT. * @DAMOS_HUGEPAGE: Call ``madvise()`` for the region with MADV_HUGEPAGE. * @DAMOS_NOHUGEPAGE: Call ``madvise()`` for the region with MADV_NOHUGEPAGE. +* @DAMOS_DEMOTE: Migrate cold pages from fast memory node (DRAM) to slow +* memory node (persistent memory). * @DAMOS_STAT: Do nothing but count the stat. */ enum damos_action {
@@ -96,6 +98,7 @@ enum damos_action {DAMOS_HUGEPAGE ,DAMOS_NOHUGEPAGE ,DAMOS_STAT ,/* Do nothing but only record the stat */ + DAMOS_DEMOTE, };/**
mm/damon/dbgfs.c +1 -0
@@ -169,6 +169,7 @@ static bool damos_action_valid(int action)case DAMOS_HUGEPAGE :case DAMOS_NOHUGEPAGE :case DAMOS_STAT : +case DAMOS_DEMOTE :return true;default :return false;
mm/damon/vaddr.c +147 -0
165 lines not on this page · raw message
Signature · 1 line
1.8.3.1
Andrew Morton
maintainerQuoted 7 lines · On Wed, 22 Dec 2021 19:14:39 +0800 Baolin Wang <[email protected]>…
Now on tiered memory system with different memory types, the reclaim path in
shrink_page_list()already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.
Quoted 6 lines
We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
This patch set introduces a new scheme named
DAMOS_DEMOTEto support this feature, and works well from my testing. Any comments are welcome. Thanks.
This is interesting.
I think it would be helpful if we could have some example scenarios in this changelog, help people understand how to use DAMOS_DEMOTE and what effects it has.
Documentation/admin-guide/mm/damon/usage.rst would like an update?
And the DAMON user space tool?
Baolin Wang
reviewerQuoted 13 lines · Andrew Morton
Quoted 11 lines · On Wed, 22 Dec 2021 19:14:39 +0800 Baolin Wang <[email protected]>…
Now on tiered memory system with different memory types, the reclaim path in
shrink_page_list()already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
Quoted 8 lines
Quoted 2 lines
This patch set introduces a new scheme named
DAMOS_DEMOTEto support this feature, and works well from my testing. Any comments are welcome. Thanks.This is interesting.
I think it would be helpful if we could have some example scenarios in this changelog, help people understand how to use
DAMOS_DEMOTEand what effects it has.
Sure.
Quoted 2 lines
Documentation/admin-guide/mm/damon/usage.rstwould like an update?
Ah, I missed updating de Doc, and will do in v3.
Quoted 1 line
And the DAMON user space tool?
Yes. Thanks for your comments.
Quoted 9 lines · Baolin Wang
Hi,
Now on tiered memory system with different memory types, the reclaim path in
shrink_page_list()already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.
Quoted 6 lines
We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
This patch set introduces a new scheme named
DAMOS_DEMOTEto support this feature, and works well from my testing. Any comments are welcome. Thanks.
As a performance optimization patch, it's better to provide some test results.
Another question is why we shouldn't do this in user space? With DAMON, it's possible to export cold memory regions information to the user space, then we can use move_pages() to migrate them from DRAM to PMEM. What's the problem of that?
Best Regards,
Huang, Ying
Quoted 19 lines
Changes from v1:
- Reuse thedemote_page_list().
- Fix some comments style issues.
- Move theDAMOS_DEMOTEdefinition to the correct place.
- Rename some function name.
- Change to return void type fordamos_isolate_page().
- Remove unnecessaryPAGE_ALIGN()indamos_demote().
- Fix the return value fordamos_demote().Baolin Wang (2):
mm: Export thedemote_page_list()function
mm/damon: Add a new scheme to support demotion on tiered memory systeminclude/linux/damon.h | 3 ++ mm/damon/dbgfs.c | 1 + mm/damon/vaddr.c | 147 ++++++++++++++++++++++++++++++++++++++++++++++++++ mm/internal.h | 2 + mm/vmscan.c | 4 +- 5 files changed, 155 insertions(+), 2 deletions(-)
Baolin Wang
reviewerQuoted 15 lines · Ying
Quoted 13 lines · Baolin Wang
Hi,
Now on tiered memory system with different memory types, the reclaim path in
shrink_page_list()already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
Quoted 5 lines
Quoted 2 lines
This patch set introduces a new scheme named
DAMOS_DEMOTEto support this feature, and works well from my testing. Any comments are welcome. Thanks.As a performance optimization patch, it's better to provide some test results.
Actually this is a functional patch, which adds a new scheme for DAMON. And I think it is too early to measure the performance for the real workload, and more work need to do for DAMON used on tiered memory system (like supporting promotion scheme later).
Quoted 4 lines
Another question is why we shouldn't do this in user space? With DAMON, it's possible to export cold memory regions information to the user space, then we can use
move_pages()to migrate them from DRAM to PMEM. What's the problem of that?
IMO this is the purpose of introducing scheme for DAMON, and you can check more in the Documentation/admin-guide/mm/damon/usage.rst.
"
Schemes
-------
For usual DAMON-based data access aware memory management optimizations, users would simply want the system to apply a memory management action to a memory region of a specific access pattern. DAMON receives such formalized operation schemes from the user and applies those to the target processes. "
Quoted 18 lines · Baolin Wang
Quoted 17 lines · Ying
Quoted 15 lines · Baolin Wang
Hi,
Now on tiered memory system with different memory types, the reclaim path in
shrink_page_list()already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
This patch set introduces a new scheme named
DAMOS_DEMOTEto support this feature, and works well from my testing. Any comments are welcome. Thanks.
Quoted 8 lines
Quoted 3 lines
As a performance optimization patch, it's better to provide some test
results.Actually this is a functional patch, which adds a new scheme for DAMON. And I think it is too early to measure the performance for the real workload, and more work need to do for DAMON used on tiered memory system (like supporting promotion scheme later).
I don't think you provide any new functionality except the performance influence.
And I think proactive demotion itself can show some performance benefit already. Just like we can find the performance benefit in the proactive reclaim patchset as below.
https://lore.kernel.org/lkml/[email protected]/
Quoted 12 lines
Quoted 4 lines
Another question is why we shouldn't do this in user space? With DAMON, it's possible to export cold memory regions information to the user space, then we can use
move_pages()to migrate them from DRAM to PMEM. What's the problem of that?IMO this is the purpose of introducing scheme for DAMON, and you can check more in the
Documentation/admin-guide/mm/damon/usage.rst."
Schemes
-------
Quoted 7 lines
For usual DAMON-based data access aware memory management optimizations, users
would simply want the system to apply a memory management action to a memory region of a specific access pattern. DAMON receives such formalized operation
schemes from the user and applies those to the target processes. "
For proactive reclaim, we haven't a user space ABI to reclaim a page of a process from memory to disk. So it appears necessary to add a kernel module to do that.
But for proactive demotion, we already have a user space ABI (move_pages()) to demote a page of a process from DRAM to PMEM. What prevents you to do all these in the user space?
And, I found there are MADV_XXX schemes too. Where the user space ABIs are available already. TBH, I don't know why we need these given there are already user space ABIs. Maybe this is a question for SeongJae too.
Best Regards,
Huang, Ying
Baolin Wang
reviewerQuoted 24 lines · Ying
Quoted 22 lines · Baolin Wang
Quoted 20 lines · Ying
Quoted 9 lines · Baolin Wang
Hi,
Now on tiered memory system with different memory types, the reclaim path in
shrink_page_list()already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.Quoted 6 lines
We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
This patch set introduces a new scheme named
DAMOS_DEMOTEto support this feature, and works well from my testing. Any comments are welcome. Thanks.As a performance optimization patch, it's better to provide some test
results.
Quoted 7 lines
Quoted 4 lines
Actually this is a functional patch, which adds a new scheme for DAMON. And I think it is too early to measure the performance for the real workload, and more work need to do for DAMON used on tiered memory system (like supporting promotion scheme later).
I don't think you provide any new functionality except the performance influence.
Fair enough. I mean for DAMON.
Quoted 2 lines
And I think proactive demotion itself can show some performance benefit already. Just like we can find the performance benefit in the proactive
Yes, I think so too. But now I am afraid I can not get some obvious performance benefit with current linux-next branch on tiered memory system, since the promotion patches are not there (yes, I can backport them into my local branch to test), meanwhile I may need more tuning for the demote scheme (such as tuning min-size, max-size, min-acc, max-acc, min-age, max-age to get a better performance) for the real workload. Now I just did a small step to add demotiong support for DAMON, so I do not expect some obvious performance gain now (more work need to research). But same as the proactive reclaim, I think this is on the right way for DAMON.
Anyway, maybe some other people also curious the benefit, and I will do some measurement with DAMON demote scheme on mysql to show the performance results. Or do you have any other measurement suggestion?
Quoted 28 lines
reclaim patchset as below.
https://lore.kernel.org/lkml/[email protected]/
Quoted 12 lines
Quoted 4 lines
Another question is why we shouldn't do this in user space? With DAMON, it's possible to export cold memory regions information to the user space, then we can use
move_pages()to migrate them from DRAM to PMEM. What's the problem of that?IMO this is the purpose of introducing scheme for DAMON, and you can check more in the
Documentation/admin-guide/mm/damon/usage.rst."
Schemes
-------Quoted 7 lines
For usual DAMON-based data access aware memory management optimizations, users
would simply want the system to apply a memory management action to a memory region of a specific access pattern. DAMON receives such formalized operation
schemes from the user and applies those to the target processes. "For proactive reclaim, we haven't a user space ABI to reclaim a page of a process from memory to disk. So it appears necessary to add a kernel module to do that.
Quoted 7 lines
But for proactive demotion, we already have a user space ABI (
move_pages()) to demote a page of a process from DRAM to PMEM. What prevents you to do all these in the user space?And, I found there are
MADV_XXXschemes too. Where the user space ABIs are available already. TBH, I don't know why we need these given there are already user space ABIs. Maybe this is a question for SeongJae too.
From my understanding, schemes will simplify the design for user space to avoid implementing their own strategy according to the monitoring results, and more details in patch[1]. SeongJae may have more input for the purpose.
Quoted 49 lines · Baolin Wang
Quoted 24 lines · Ying
Quoted 22 lines · Baolin Wang
Quoted 20 lines · Ying
Quoted 9 lines · Baolin Wang
Hi,
Now on tiered memory system with different memory types, the reclaim path in
shrink_page_list()already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.Quoted 6 lines
We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
This patch set introduces a new scheme named
DAMOS_DEMOTEto support this feature, and works well from my testing. Any comments are welcome. Thanks.As a performance optimization patch, it's better to provide some test
results.Quoted 7 lines
Quoted 4 lines
Actually this is a functional patch, which adds a new scheme for DAMON. And I think it is too early to measure the performance for the real workload, and more work need to do for DAMON used on tiered memory system (like supporting promotion scheme later).
I don't think you provide any new functionality except the performance
influence.Fair enough. I mean for DAMON.
Quoted 2 lines
And I think proactive demotion itself can show some performance benefit already. Just like we can find the performance benefit in the proactive
Yes, I think so too. But now I am afraid I can not get some obvious performance benefit with current linux-next branch on tiered memory system, since the promotion patches are not there (yes, I can backport them into my local branch to test), meanwhile I may need more tuning for the demote scheme (such as tuning min-size, max-size, min-acc, max-acc, min-age, max-age to get a better performance) for the real workload. Now I just did a small step to add demotiong support for DAMON, so I do not expect some obvious performance gain now (more work need to research). But same as the proactive reclaim, I think this is on the right way for DAMON.
Quoted 3 lines
Anyway, maybe some other people also curious the benefit, and I will do some measurement with DAMON demote scheme on mysql to show the performance results. Or do you have any other measurement suggestion?
For example, you can run 2 instances of workload, say, instance A and instance B. The memory size of instance A + B is larger than the size of the DRAM. And numactl -m <DRAM node> is used to run the instance, so that demotion will be triggered when DRAM is used up. Instance A is run at first, after some time, say several to tens seconds, instance B is run. With the original kernel, demotion will be triggered when run instance B, long latency may be triggered. With your patch, the proactive demotion will be triggered earlier to avoid the long latency at the cost of performance of instance A (may be just a little). We can also compare between DAMON based and the in-kernel LRU based cold page identification algorithm.
Quoted 34 lines
Quoted 22 lines
reclaim patchset as below.
https://lore.kernel.org/lkml/[email protected]/Quoted 12 lines
Quoted 4 lines
Another question is why we shouldn't do this in user space? With DAMON, it's possible to export cold memory regions information to the user space, then we can use
move_pages()to migrate them from DRAM to PMEM. What's the problem of that?IMO this is the purpose of introducing scheme for DAMON, and you can check more in the
Documentation/admin-guide/mm/damon/usage.rst."
Schemes
-------Quoted 7 lines
For usual DAMON-based data access aware memory management optimizations, users
would simply want the system to apply a memory management action to a memory region of a specific access pattern. DAMON receives such formalized operation
schemes from the user and applies those to the target processes. "Quoted 11 lines
For proactive reclaim, we haven't a user space ABI to reclaim a page of
a process from memory to disk. So it appears necessary to add a kernel module to do that.
But for proactive demotion, we already have a user space ABI (move_pages()) to demote a page of a process from DRAM to PMEM. What prevents you to do all these in the user space?
And, I found there areMADV_XXXschemes too. Where the user space ABIs
are available already. TBH, I don't know why we need these given there are already user space ABIs. Maybe this is a question for SeongJae too.
Quoted 7 lines
From my understanding, schemes will simplify the design for user space to avoid implementing their own strategy according to the monitoring results, and more details in patch[1]. SeongJae may have more input for the purpose.
Thanks a lot for your information. The commit log is helpful.
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON + madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information + process_madvise()).
And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have process_madvise() for that before DAMON. Some more complex algorithm may be needed for some applications.
And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
Best Regards,
Huang, Ying
SeongJae Park
maintainerHi,
Quoted 55 lines · Ying
Quoted 49 lines · Baolin Wang
Quoted 24 lines · Ying
Quoted 22 lines · Baolin Wang
Quoted 20 lines · Ying
Quoted 9 lines · Baolin Wang
Hi,
Now on tiered memory system with different memory types, the reclaim path in
shrink_page_list()already support demoting pages to slow memory node instead of discarding the pages. However, at that time the fast memory node memory wartermark is already tense, which will increase the memory allocation latency during page demotion. So a new method from user space demoting cold pages proactively will be more helpful.Quoted 6 lines
We can rely on the DAMON in user space to help to monitor the cold memory on fast memory node, and demote the cold pages to slow memory node proactively to keep the fast memory node in a healthy state.
This patch set introduces a new scheme named
DAMOS_DEMOTEto support this feature, and works well from my testing. Any comments are welcome. Thanks.As a performance optimization patch, it's better to provide some test
results.Quoted 7 lines
Quoted 4 lines
Actually this is a functional patch, which adds a new scheme for DAMON. And I think it is too early to measure the performance for the real workload, and more work need to do for DAMON used on tiered memory system (like supporting promotion scheme later).
I don't think you provide any new functionality except the performance
influence.Fair enough. I mean for DAMON.
Quoted 2 lines
And I think proactive demotion itself can show some performance benefit already. Just like we can find the performance benefit in the proactive
Yes, I think so too. But now I am afraid I can not get some obvious performance benefit with current linux-next branch on tiered memory system, since the promotion patches are not there (yes, I can backport them into my local branch to test), meanwhile I may need more tuning for the demote scheme (such as tuning min-size, max-size, min-acc, max-acc, min-age, max-age to get a better performance) for the real workload. Now I just did a small step to add demotiong support for DAMON, so I do not expect some obvious performance gain now (more work need to research). But same as the proactive reclaim, I think this is on the right way for DAMON.
Quoted 3 lines
Anyway, maybe some other people also curious the benefit, and I will do some measurement with DAMON demote scheme on mysql to show the performance results. Or do you have any other measurement suggestion?
Quoted 11 lines
For example, you can run 2 instances of workload, say, instance A and instance B. The memory size of instance A + B is larger than the size of the DRAM. And
numactl -m <DRAM node>is used to run the instance, so that demotion will be triggered when DRAM is used up. Instance A is run at first, after some time, say several to tens seconds, instance B is run. With the original kernel, demotion will be triggered when run instance B, long latency may be triggered. With your patch, the proactive demotion will be triggered earlier to avoid the long latency at the cost of performance of instance A (may be just a little). We can also compare between DAMON based and the in-kernel LRU based cold page identification algorithm.
Good suggestion!
Also, there is a performance test for virtual address space proactive reclamation scheme in the DAMON performance tests suite[1]. It measures memory saving and runtime slowdown. Maybe you could start from extending that for demote scheme and measure similar metrics.
[1] https://github.com/awslabs/damon-tests/tree/master/perf
Quoted 65 lines
Quoted 35 lines
Quoted 23 lines
reclaim patchset as below.
https://lore.kernel.org/lkml/[email protected]/Quoted 12 lines
Quoted 4 lines
Another question is why we shouldn't do this in user space? With DAMON, it's possible to export cold memory regions information to the user space, then we can use
move_pages()to migrate them from DRAM to PMEM. What's the problem of that?IMO this is the purpose of introducing scheme for DAMON, and you can check more in the
Documentation/admin-guide/mm/damon/usage.rst."
Schemes
-------Quoted 7 lines
For usual DAMON-based data access aware memory management optimizations, users
would simply want the system to apply a memory management action to a memory region of a specific access pattern. DAMON receives such formalized operation
schemes from the user and applies those to the target processes. "Quoted 11 lines
For proactive reclaim, we haven't a user space ABI to reclaim a page of
a process from memory to disk. So it appears necessary to add a kernel module to do that.
But for proactive demotion, we already have a user space ABI (move_pages()) to demote a page of a process from DRAM to PMEM. What prevents you to do all these in the user space?
And, I found there areMADV_XXXschemes too. Where the user space ABIs
are available already. TBH, I don't know why we need these given there are already user space ABIs. Maybe this is a question for SeongJae too.Quoted 7 lines
From my understanding, schemes will simplify the design for user space to avoid implementing their own strategy according to the monitoring results, and more details in patch[1]. SeongJae may have more input for the purpose.
Thanks a lot for your information. The commit log is helpful.
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON +
madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information +process_madvise()).And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have
process_madvise()for that before DAMON. Some more complex algorithm may be needed for some applications.And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
Quoted 2 lines
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
I basically agree to Ying, as I also noted in the coverletter of DAMOS patchset[1]:
DAMON[1] can be used as a primitive for data access aware memory management optimizations. For that, users who want such optimizations should run DAMON, read the monitoring results, analyze it, plan a new memory management scheme, and apply the new scheme by themselves. Such efforts will be inevitable for some complicated optimizations.
That is, I believe some programs and big companies would definitely have their own information and want such kind of complicated optimizations. But, such optimizations would depend on characteristics of each program and require investment of some amount of resources. Some other programs and users wouldn't have such special information, and/or resource to invest for such optimizations. For them, some amount of benefit would be helpful enough even though its sub-optimal.
I think we should help both groups, and DAMOS could be useful for the second group. And I don't think DAMOS is useless for the first group. They could use their information-based policy in prallel to DAMOS in some cases. E.g., if they have a way to predict the data access pattern of specific memory region even without help from DAMON, they can use their own policy for the region but DAMOS for other regions.
Someone could ask why not implement a user-space implementation for the second group, then. First of all, DAMOS is not only for the user-space driven virtual memory management optimization, but also for kernel-space programs and any DAMOS-supportable address spaces including the physical address space. And, another important goal of DAMOS for user space driven use case in addition to reducing the redundant code is minimizing the user-kernel context switch overhead for passing the monitoring results information and memory management action requests.
In summary, I agree the user space per-application policy daemon will be useful for the specialized ultimate optimizations, but we also need DAMOS for another common group of cases.
If I'm missing something, please feel free to let me know.
Thanks,
SJ
Quoted 3 lines
Best Regards,
Huang, Ying
Hi, SeongJae,
Quoted 3 lines · SeongJae Park
Hi,
On Thu, 23 Dec 2021 15:51:18 +0800 "Huang, Ying" <[email protected]> wrote:
[snip]
Quoted 58 lines
Quoted 20 lines
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON +
madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information +process_madvise()).And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have
process_madvise()for that before DAMON. Some more complex algorithm may be needed for some applications.And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
Quoted 2 lines
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
I basically agree to Ying, as I also noted in the coverletter of DAMOS patchset[1]:
DAMON[1] can be used as a primitive for data access aware memory management optimizations. For that, users who want such optimizations should run DAMON, read the monitoring results, analyze it, plan a new memory management scheme, and apply the new scheme by themselves. Such efforts will be inevitable for some complicated optimizations.
That is, I believe some programs and big companies would definitely have their own information and want such kind of complicated optimizations. But, such optimizations would depend on characteristics of each program and require investment of some amount of resources. Some other programs and users wouldn't have such special information, and/or resource to invest for such optimizations. For them, some amount of benefit would be helpful enough even though its sub-optimal.
I think we should help both groups, and DAMOS could be useful for the second group. And I don't think DAMOS is useless for the first group. They could use their information-based policy in prallel to DAMOS in some cases. E.g., if they have a way to predict the data access pattern of specific memory region even without help from DAMON, they can use their own policy for the region but DAMOS for other regions.
Someone could ask why not implement a user-space implementation for the second group, then. First of all, DAMOS is not only for the user-space driven virtual memory management optimization, but also for kernel-space programs and any DAMOS-supportable address spaces including the physical address space. And, another important goal of DAMOS for user space driven use case in addition to reducing the redundant code is minimizing the user-kernel context switch overhead for passing the monitoring results information and memory management action requests.
Quoted 5 lines
In summary, I agree the user space per-application policy daemon will be useful for the specialized ultimate optimizations, but we also need DAMOS for another common group of cases.
If I'm missing something, please feel free to let me know.
I guess that most end-users and quite some system administrators of small companies have no enough capability to take advantage of the per-application optimizations. How do they know the appropriate region number and proactive reclaim threshold?
So per my understanding, Linux kernel
need provide,
1. An in-kernel general policy that is obviously correct and benefits almost all users and applications, at least no regression. No complex configuration or deep knowledge is needed to take advantage of it.
2. Some way to inspect and control system and application behavior, so that some advanced and customized user space policy daemons can be built to satisfy some advanced users who have the enough knowledge for the applications and systems, for example, oomd.
Best Regards,
Huang, Ying
SeongJae Park
maintainerHello,
Quoted 87 lines · Ying
Hi, SeongJae,
Quoted 3 lines · SeongJae Park
Hi,
On Thu, 23 Dec 2021 15:51:18 +0800 "Huang, Ying" <[email protected]> wrote:
[snip]
Quoted 58 lines
Quoted 20 lines
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON +
madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information +process_madvise()).And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have
process_madvise()for that before DAMON. Some more complex algorithm may be needed for some applications.And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
Quoted 2 lines
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
I basically agree to Ying, as I also noted in the coverletter of DAMOS patchset[1]:
DAMON[1] can be used as a primitive for data access aware memory management optimizations. For that, users who want such optimizations should run DAMON, read the monitoring results, analyze it, plan a new memory management scheme, and apply the new scheme by themselves. Such efforts will be inevitable for some complicated optimizations.
That is, I believe some programs and big companies would definitely have their own information and want such kind of complicated optimizations. But, such optimizations would depend on characteristics of each program and require investment of some amount of resources. Some other programs and users wouldn't have such special information, and/or resource to invest for such optimizations. For them, some amount of benefit would be helpful enough even though its sub-optimal.
I think we should help both groups, and DAMOS could be useful for the second group. And I don't think DAMOS is useless for the first group. They could use their information-based policy in prallel to DAMOS in some cases. E.g., if they have a way to predict the data access pattern of specific memory region even without help from DAMON, they can use their own policy for the region but DAMOS for other regions.
Someone could ask why not implement a user-space implementation for the second group, then. First of all, DAMOS is not only for the user-space driven virtual memory management optimization, but also for kernel-space programs and any DAMOS-supportable address spaces including the physical address space. And, another important goal of DAMOS for user space driven use case in addition to reducing the redundant code is minimizing the user-kernel context switch overhead for passing the monitoring results information and memory management action requests.
Quoted 5 lines
In summary, I agree the user space per-application policy daemon will be useful for the specialized ultimate optimizations, but we also need DAMOS for another common group of cases.
If I'm missing something, please feel free to let me know.
I guess that most end-users and quite some system administrators of small companies have no enough capability to take advantage of the per-application optimizations. How do they know the appropriate region number and proactive reclaim threshold?
So per my understanding, Linux kernel
need provide,1. An in-kernel general policy that is obviously correct and benefits almost all users and applications, at least no regression. No complex configuration or deep knowledge is needed to take advantage of it.
Quoted 4 lines
2. Some way to inspect and control system and application behavior, so that some advanced and customized user space policy daemons can be built to satisfy some advanced users who have the enough knowledge for the applications and systems, for example, oomd.
Agreed, and I think that's the approach that DAMON is currently taking. In specific, we provide DAMON debugfs interface for users who want to inspect and control their system and application behavior. Using it, we also made a PoC level user space policy daemon[1].
For the in-kernel policies, we are developing DAMON-based kernel components one by one, for specific usages. DAMON-based proactive reclamation module (DAMON_RECLAIM) is one such example. Such DAMON-based components will remove complex tunables that necessary for the general inspection and control of the system but unnecessary for their specific purpose (e.g., proactive reclamation) to allow users use it in a simple manner. Also, those will use conservative default configs to not incur visible regression. For example, DAMON_RECLAIM uses only up to 1% of single CPU time for the reclamation by default.
In short, I think we're on the same page, and adding DEMOTION scheme action could be helpful for the users who want to efficiently inspect and control the system/application behavior for their tiered memory systems. It's unclear how much benefit this could give to users, though. I assume Baolin would come back with some sort of numbers in the next spin. Nevertheless, I personally don't think that's a critical blocker, as this patch is essentially just adding a way for using the pre-existing primitive, namely move_pages(), in a little bit more efficient manner, for the access pattern-based use cases.
If I'm missing something, please feel free to let me know.
[1] https://github.com/awslabs/damoos
Thanks,
SJ
Quoted 3 lines
Best Regards,
Huang, Ying
Quoted 101 lines · SeongJae Park
Hello,
Quoted 87 lines · Ying
Hi, SeongJae,
Quoted 3 lines · SeongJae Park
Hi,
On Thu, 23 Dec 2021 15:51:18 +0800 "Huang, Ying" <[email protected]> wrote:
[snip]
Quoted 58 lines
Quoted 20 lines
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON +
madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information +process_madvise()).And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have
process_madvise()for that before DAMON. Some more complex algorithm may be needed for some applications.And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
Quoted 2 lines
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
I basically agree to Ying, as I also noted in the coverletter of DAMOS patchset[1]:
DAMON[1] can be used as a primitive for data access aware memory management optimizations. For that, users who want such optimizations should run DAMON, read the monitoring results, analyze it, plan a new memory management scheme, and apply the new scheme by themselves. Such efforts will be inevitable for some complicated optimizations.
That is, I believe some programs and big companies would definitely have their own information and want such kind of complicated optimizations. But, such optimizations would depend on characteristics of each program and require investment of some amount of resources. Some other programs and users wouldn't have such special information, and/or resource to invest for such optimizations. For them, some amount of benefit would be helpful enough even though its sub-optimal.
I think we should help both groups, and DAMOS could be useful for the second group. And I don't think DAMOS is useless for the first group. They could use their information-based policy in prallel to DAMOS in some cases. E.g., if they have a way to predict the data access pattern of specific memory region even without help from DAMON, they can use their own policy for the region but DAMOS for other regions.
Someone could ask why not implement a user-space implementation for the second group, then. First of all, DAMOS is not only for the user-space driven virtual memory management optimization, but also for kernel-space programs and any DAMOS-supportable address spaces including the physical address space. And, another important goal of DAMOS for user space driven use case in addition to reducing the redundant code is minimizing the user-kernel context switch overhead for passing the monitoring results information and memory management action requests.
Quoted 5 lines
In summary, I agree the user space per-application policy daemon will be useful for the specialized ultimate optimizations, but we also need DAMOS for another common group of cases.
If I'm missing something, please feel free to let me know.
I guess that most end-users and quite some system administrators of small companies have no enough capability to take advantage of the per-application optimizations. How do they know the appropriate region number and proactive reclaim threshold?
So per my understanding, Linux kernel
need provide,1. An in-kernel general policy that is obviously correct and benefits almost all users and applications, at least no regression. No complex configuration or deep knowledge is needed to take advantage of it.
Quoted 4 lines
2. Some way to inspect and control system and application behavior, so that some advanced and customized user space policy daemons can be built to satisfy some advanced users who have the enough knowledge for the applications and systems, for example, oomd.
Agreed, and I think that's the approach that DAMON is currently taking. In specific, we provide DAMON debugfs interface for users who want to inspect and control their system and application behavior. Using it, we also made a PoC level user space policy daemon[1].
Quoted 8 lines
For the in-kernel policies, we are developing DAMON-based kernel components one by one, for specific usages. DAMON-based proactive reclamation module (
DAMON_RECLAIM) is one such example. Such DAMON-based components will remove complex tunables that necessary for the general inspection and control of the system but unnecessary for their specific purpose (e.g., proactive reclamation) to allow users use it in a simple manner. Also, those will use conservative default configs to not incur visible regression. For example,DAMON_RECLAIMuses only up to 1% of single CPU time for the reclamation by default.
I don't think DAMON schemes are the in-kernel general policy I mentioned above (1.). For example, NUMA balancing is a general policy to optimize performance. It tries to provide a general policy that works for all users with as few as possible tunables. If some tunables are needed, they will be provided as ABI.
Best Regards,
Huang, Ying
Quoted 20 lines
In short, I think we're on the same page, and adding DEMOTION scheme action could be helpful for the users who want to efficiently inspect and control the system/application behavior for their tiered memory systems. It's unclear how much benefit this could give to users, though. I assume Baolin would come back with some sort of numbers in the next spin. Nevertheless, I personally don't think that's a critical blocker, as this patch is essentially just adding a way for using the pre-existing primitive, namely
move_pages(), in a little bit more efficient manner, for the access pattern-based use cases.If I'm missing something, please feel free to let me know.
[1] https://github.com/awslabs/damoos
Thanks,
SJQuoted 3 lines
Best Regards,
Huang, Ying
SeongJae Park
maintainerQuoted 112 lines · Ying
Quoted 101 lines · SeongJae Park
Hello,
Quoted 87 lines · Ying
Hi, SeongJae,
Quoted 3 lines · SeongJae Park
Hi,
On Thu, 23 Dec 2021 15:51:18 +0800 "Huang, Ying" <[email protected]> wrote:
[snip]
Quoted 58 lines
Quoted 20 lines
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON +
madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information +process_madvise()).And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have
process_madvise()for that before DAMON. Some more complex algorithm may be needed for some applications.And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
Quoted 2 lines
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
I basically agree to Ying, as I also noted in the coverletter of DAMOS patchset[1]:
DAMON[1] can be used as a primitive for data access aware memory management optimizations. For that, users who want such optimizations should run DAMON, read the monitoring results, analyze it, plan a new memory management scheme, and apply the new scheme by themselves. Such efforts will be inevitable for some complicated optimizations.
That is, I believe some programs and big companies would definitely have their own information and want such kind of complicated optimizations. But, such optimizations would depend on characteristics of each program and require investment of some amount of resources. Some other programs and users wouldn't have such special information, and/or resource to invest for such optimizations. For them, some amount of benefit would be helpful enough even though its sub-optimal.
I think we should help both groups, and DAMOS could be useful for the second group. And I don't think DAMOS is useless for the first group. They could use their information-based policy in prallel to DAMOS in some cases. E.g., if they have a way to predict the data access pattern of specific memory region even without help from DAMON, they can use their own policy for the region but DAMOS for other regions.
Someone could ask why not implement a user-space implementation for the second group, then. First of all, DAMOS is not only for the user-space driven virtual memory management optimization, but also for kernel-space programs and any DAMOS-supportable address spaces including the physical address space. And, another important goal of DAMOS for user space driven use case in addition to reducing the redundant code is minimizing the user-kernel context switch overhead for passing the monitoring results information and memory management action requests.
Quoted 5 lines
In summary, I agree the user space per-application policy daemon will be useful for the specialized ultimate optimizations, but we also need DAMOS for another common group of cases.
If I'm missing something, please feel free to let me know.
I guess that most end-users and quite some system administrators of small companies have no enough capability to take advantage of the per-application optimizations. How do they know the appropriate region number and proactive reclaim threshold?
So per my understanding, Linux kernel
need provide,1. An in-kernel general policy that is obviously correct and benefits almost all users and applications, at least no regression. No complex configuration or deep knowledge is needed to take advantage of it.
Quoted 4 lines
2. Some way to inspect and control system and application behavior, so that some advanced and customized user space policy daemons can be built to satisfy some advanced users who have the enough knowledge for the applications and systems, for example, oomd.
Agreed, and I think that's the approach that DAMON is currently taking. In specific, we provide DAMON debugfs interface for users who want to inspect and control their system and application behavior. Using it, we also made a PoC level user space policy daemon[1].
Quoted 8 lines
For the in-kernel policies, we are developing DAMON-based kernel components one by one, for specific usages. DAMON-based proactive reclamation module (
DAMON_RECLAIM) is one such example. Such DAMON-based components will remove complex tunables that necessary for the general inspection and control of the system but unnecessary for their specific purpose (e.g., proactive reclamation) to allow users use it in a simple manner. Also, those will use conservative default configs to not incur visible regression. For example,DAMON_RECLAIMuses only up to 1% of single CPU time for the reclamation by default.
Quoted 5 lines
I don't think DAMON schemes are the in-kernel general policy I mentioned above (1.). For example, NUMA balancing is a general policy to optimize performance. It tries to provide a general policy that works for all users with as few as possible tunables. If some tunables are needed, they will be provided as ABI.
Exactly. What I'm saying is, DAMON schemes that exposed to user space via the debugfs interface is for inspection of system and development of user space daemon (2.). It requires some level of tuning and doesn't provide stable ABI but the debugfs interface. Meanwhile, DAMON-based kernel components like DAMON_RECLAIM can be used for the in-kernel general policy (1.). For example, DAMON_RECLAIM also tries to be beneficial or at least incur no regression for almost every users, provides as few as possible tunables, and provides those via its ABI (module parameters), not debugfs.
Thanks,
SJ
Quoted 25 lines
Best Regards,
Huang, YingQuoted 20 lines
In short, I think we're on the same page, and adding DEMOTION scheme action could be helpful for the users who want to efficiently inspect and control the system/application behavior for their tiered memory systems. It's unclear how much benefit this could give to users, though. I assume Baolin would come back with some sort of numbers in the next spin. Nevertheless, I personally don't think that's a critical blocker, as this patch is essentially just adding a way for using the pre-existing primitive, namely
move_pages(), in a little bit more efficient manner, for the access pattern-based use cases.If I'm missing something, please feel free to let me know.
[1] https://github.com/awslabs/damoos
Thanks,
SJQuoted 3 lines
Best Regards,
Huang, Ying
Quoted 120 lines · SeongJae Park
Quoted 112 lines · Ying
Quoted 101 lines · SeongJae Park
Hello,
Quoted 87 lines · Ying
Hi, SeongJae,
Quoted 3 lines · SeongJae Park
Hi,
On Thu, 23 Dec 2021 15:51:18 +0800 "Huang, Ying" <[email protected]> wrote:
[snip]
Quoted 58 lines
Quoted 20 lines
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON +
madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information +process_madvise()).And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have
process_madvise()for that before DAMON. Some more complex algorithm may be needed for some applications.And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
Quoted 2 lines
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
I basically agree to Ying, as I also noted in the coverletter of DAMOS patchset[1]:
DAMON[1] can be used as a primitive for data access aware memory management optimizations. For that, users who want such optimizations should run DAMON, read the monitoring results, analyze it, plan a new memory management scheme, and apply the new scheme by themselves. Such efforts will be inevitable for some complicated optimizations.
That is, I believe some programs and big companies would definitely have their own information and want such kind of complicated optimizations. But, such optimizations would depend on characteristics of each program and require investment of some amount of resources. Some other programs and users wouldn't have such special information, and/or resource to invest for such optimizations. For them, some amount of benefit would be helpful enough even though its sub-optimal.
I think we should help both groups, and DAMOS could be useful for the second group. And I don't think DAMOS is useless for the first group. They could use their information-based policy in prallel to DAMOS in some cases. E.g., if they have a way to predict the data access pattern of specific memory region even without help from DAMON, they can use their own policy for the region but DAMOS for other regions.
Someone could ask why not implement a user-space implementation for the second group, then. First of all, DAMOS is not only for the user-space driven virtual memory management optimization, but also for kernel-space programs and any DAMOS-supportable address spaces including the physical address space. And, another important goal of DAMOS for user space driven use case in addition to reducing the redundant code is minimizing the user-kernel context switch overhead for passing the monitoring results information and memory management action requests.
Quoted 5 lines
In summary, I agree the user space per-application policy daemon will be useful for the specialized ultimate optimizations, but we also need DAMOS for another common group of cases.
If I'm missing something, please feel free to let me know.
I guess that most end-users and quite some system administrators of small companies have no enough capability to take advantage of the per-application optimizations. How do they know the appropriate region number and proactive reclaim threshold?
So per my understanding, Linux kernel
need provide,1. An in-kernel general policy that is obviously correct and benefits almost all users and applications, at least no regression. No complex configuration or deep knowledge is needed to take advantage of it.
Quoted 4 lines
2. Some way to inspect and control system and application behavior, so that some advanced and customized user space policy daemons can be built to satisfy some advanced users who have the enough knowledge for the applications and systems, for example, oomd.
Agreed, and I think that's the approach that DAMON is currently taking. In specific, we provide DAMON debugfs interface for users who want to inspect and control their system and application behavior. Using it, we also made a PoC level user space policy daemon[1].
Quoted 8 lines
For the in-kernel policies, we are developing DAMON-based kernel components one by one, for specific usages. DAMON-based proactive reclamation module (
DAMON_RECLAIM) is one such example. Such DAMON-based components will remove complex tunables that necessary for the general inspection and control of the system but unnecessary for their specific purpose (e.g., proactive reclamation) to allow users use it in a simple manner. Also, those will use conservative default configs to not incur visible regression. For example,DAMON_RECLAIMuses only up to 1% of single CPU time for the reclamation by default.Quoted 5 lines
I don't think DAMON schemes are the in-kernel general policy I mentioned above (1.). For example, NUMA balancing is a general policy to optimize performance. It tries to provide a general policy that works for all users with as few as possible tunables. If some tunables are needed, they will be provided as ABI.
Quoted 8 lines
Exactly. What I'm saying is, DAMON schemes that exposed to user space via the debugfs interface is for inspection of system and development of user space daemon (2.). It requires some level of tuning and doesn't provide stable ABI but the debugfs interface. Meanwhile, DAMON-based kernel components like
DAMON_RECLAIMcan be used for the in-kernel general policy (1.). For example,DAMON_RECLAIMalso tries to be beneficial or at least incur no regression for almost every users, provides as few as possible tunables, and provides those via its ABI (module parameters), not debugfs.
Thanks for your detailed explanation.
Per my understanding, DAMON schemes are kind of building blocks of some kernel feature such as DAMON_RECLAIM. Whether do we need a new scheme depends on whether it's useful as part of some kernel feature. Do you agree?
Best Regards,
Huang, Ying
Quoted 28 lines
Thanks,
SJQuoted 25 lines
Best Regards,
Huang, YingQuoted 20 lines
In short, I think we're on the same page, and adding DEMOTION scheme action could be helpful for the users who want to efficiently inspect and control the system/application behavior for their tiered memory systems. It's unclear how much benefit this could give to users, though. I assume Baolin would come back with some sort of numbers in the next spin. Nevertheless, I personally don't think that's a critical blocker, as this patch is essentially just adding a way for using the pre-existing primitive, namely
move_pages(), in a little bit more efficient manner, for the access pattern-based use cases.If I'm missing something, please feel free to let me know.
[1] https://github.com/awslabs/damoos
Thanks,
SJQuoted 3 lines
Best Regards,
Huang, Ying
SeongJae Park
maintainerQuoted 131 lines · Ying
Quoted 120 lines · SeongJae Park
Quoted 112 lines · Ying
Quoted 101 lines · SeongJae Park
Hello,
Quoted 87 lines · Ying
Hi, SeongJae,
Quoted 3 lines · SeongJae Park
Hi,
On Thu, 23 Dec 2021 15:51:18 +0800 "Huang, Ying" <[email protected]> wrote:
[snip]
Quoted 58 lines
Quoted 20 lines
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON +
madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information +process_madvise()).And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have
process_madvise()for that before DAMON. Some more complex algorithm may be needed for some applications.And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
Quoted 2 lines
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
I basically agree to Ying, as I also noted in the coverletter of DAMOS patchset[1]:
DAMON[1] can be used as a primitive for data access aware memory management optimizations. For that, users who want such optimizations should run DAMON, read the monitoring results, analyze it, plan a new memory management scheme, and apply the new scheme by themselves. Such efforts will be inevitable for some complicated optimizations.
That is, I believe some programs and big companies would definitely have their own information and want such kind of complicated optimizations. But, such optimizations would depend on characteristics of each program and require investment of some amount of resources. Some other programs and users wouldn't have such special information, and/or resource to invest for such optimizations. For them, some amount of benefit would be helpful enough even though its sub-optimal.
I think we should help both groups, and DAMOS could be useful for the second group. And I don't think DAMOS is useless for the first group. They could use their information-based policy in prallel to DAMOS in some cases. E.g., if they have a way to predict the data access pattern of specific memory region even without help from DAMON, they can use their own policy for the region but DAMOS for other regions.
Someone could ask why not implement a user-space implementation for the second group, then. First of all, DAMOS is not only for the user-space driven virtual memory management optimization, but also for kernel-space programs and any DAMOS-supportable address spaces including the physical address space. And, another important goal of DAMOS for user space driven use case in addition to reducing the redundant code is minimizing the user-kernel context switch overhead for passing the monitoring results information and memory management action requests.
Quoted 5 lines
In summary, I agree the user space per-application policy daemon will be useful for the specialized ultimate optimizations, but we also need DAMOS for another common group of cases.
If I'm missing something, please feel free to let me know.
I guess that most end-users and quite some system administrators of small companies have no enough capability to take advantage of the per-application optimizations. How do they know the appropriate region number and proactive reclaim threshold?
So per my understanding, Linux kernel
need provide,1. An in-kernel general policy that is obviously correct and benefits almost all users and applications, at least no regression. No complex configuration or deep knowledge is needed to take advantage of it.
Quoted 4 lines
2. Some way to inspect and control system and application behavior, so that some advanced and customized user space policy daemons can be built to satisfy some advanced users who have the enough knowledge for the applications and systems, for example, oomd.
Agreed, and I think that's the approach that DAMON is currently taking. In specific, we provide DAMON debugfs interface for users who want to inspect and control their system and application behavior. Using it, we also made a PoC level user space policy daemon[1].
Quoted 8 lines
For the in-kernel policies, we are developing DAMON-based kernel components one by one, for specific usages. DAMON-based proactive reclamation module (
DAMON_RECLAIM) is one such example. Such DAMON-based components will remove complex tunables that necessary for the general inspection and control of the system but unnecessary for their specific purpose (e.g., proactive reclamation) to allow users use it in a simple manner. Also, those will use conservative default configs to not incur visible regression. For example,DAMON_RECLAIMuses only up to 1% of single CPU time for the reclamation by default.Quoted 5 lines
I don't think DAMON schemes are the in-kernel general policy I mentioned above (1.). For example, NUMA balancing is a general policy to optimize performance. It tries to provide a general policy that works for all users with as few as possible tunables. If some tunables are needed, they will be provided as ABI.
Quoted 8 lines
Exactly. What I'm saying is, DAMON schemes that exposed to user space via the debugfs interface is for inspection of system and development of user space daemon (2.). It requires some level of tuning and doesn't provide stable ABI but the debugfs interface. Meanwhile, DAMON-based kernel components like
DAMON_RECLAIMcan be used for the in-kernel general policy (1.). For example,DAMON_RECLAIMalso tries to be beneficial or at least incur no regression for almost every users, provides as few as possible tunables, and provides those via its ABI (module parameters), not debugfs.
Quoted 4 lines
Thanks for your detailed explanation.
Per my understanding, DAMON schemes are kind of building blocks of some kernel feature such as
DAMON_RECLAIM.
I pretty sure you're perfectly understanding my point.
Quoted 2 lines
Whether do we need a new scheme depends on whether it's useful as part of some kernel feature. Do you agree?
Yes, agreed.
Thanks,
SJ
Quoted 32 lines
Best Regards,
Huang, YingQuoted 28 lines
Thanks,
SJQuoted 25 lines
Best Regards,
Huang, YingQuoted 20 lines
In short, I think we're on the same page, and adding DEMOTION scheme action could be helpful for the users who want to efficiently inspect and control the system/application behavior for their tiered memory systems. It's unclear how much benefit this could give to users, though. I assume Baolin would come back with some sort of numbers in the next spin. Nevertheless, I personally don't think that's a critical blocker, as this patch is essentially just adding a way for using the pre-existing primitive, namely
move_pages(), in a little bit more efficient manner, for the access pattern-based use cases.If I'm missing something, please feel free to let me know.
[1] https://github.com/awslabs/damoos
Thanks,
SJQuoted 3 lines
Best Regards,
Huang, Ying
Baolin Wang
reviewerQuoted 110 lines · SeongJae Park
Hello,
Quoted 87 lines · Ying
Hi, SeongJae,
Quoted 3 lines · SeongJae Park
Hi,
On Thu, 23 Dec 2021 15:51:18 +0800 "Huang, Ying" <[email protected]> wrote:
[snip]
Quoted 58 lines
Quoted 20 lines
It's good to avoid to change the source code of an application to apply some memory management optimization (for example, use DAMON +
madvise()). But it's much easier to run a user space daemon to optimize for the application. (for example, use DAMON + other information +process_madvise()).And this kind of per-application optimization is kind of application specific policy. This kind of policy may be too complex and flexible to be put in the kernel directly. For example, in addition to DAMON, some other application specific or system knowledge may be helpful too, so we have
process_madvise()for that before DAMON. Some more complex algorithm may be needed for some applications.And this kind of application specific policy usually need complex configuration. It's hard to export all these policy parameters to the user space as the kernel ABI. Now, DAMON schemes parameters are exported in debugfs so they are not considered ABI. So they may be changed at any time. But applications need some stable and well-maintained ABI.
Quoted 2 lines
All in all, IMHO, what we need is a user space per-application policy daemon with the information from DAMON and other sources.
I basically agree to Ying, as I also noted in the coverletter of DAMOS patchset[1]:
DAMON[1] can be used as a primitive for data access aware memory management optimizations. For that, users who want such optimizations should run DAMON, read the monitoring results, analyze it, plan a new memory management scheme, and apply the new scheme by themselves. Such efforts will be inevitable for some complicated optimizations.
That is, I believe some programs and big companies would definitely have their own information and want such kind of complicated optimizations. But, such optimizations would depend on characteristics of each program and require investment of some amount of resources. Some other programs and users wouldn't have such special information, and/or resource to invest for such optimizations. For them, some amount of benefit would be helpful enough even though its sub-optimal.
I think we should help both groups, and DAMOS could be useful for the second group. And I don't think DAMOS is useless for the first group. They could use their information-based policy in prallel to DAMOS in some cases. E.g., if they have a way to predict the data access pattern of specific memory region even without help from DAMON, they can use their own policy for the region but DAMOS for other regions.
Someone could ask why not implement a user-space implementation for the second group, then. First of all, DAMOS is not only for the user-space driven virtual memory management optimization, but also for kernel-space programs and any DAMOS-supportable address spaces including the physical address space. And, another important goal of DAMOS for user space driven use case in addition to reducing the redundant code is minimizing the user-kernel context switch overhead for passing the monitoring results information and memory management action requests.
Quoted 5 lines
In summary, I agree the user space per-application policy daemon will be useful for the specialized ultimate optimizations, but we also need DAMOS for another common group of cases.
If I'm missing something, please feel free to let me know.
I guess that most end-users and quite some system administrators of small companies have no enough capability to take advantage of the per-application optimizations. How do they know the appropriate region number and proactive reclaim threshold?
So per my understanding, Linux kernel
need provide,1. An in-kernel general policy that is obviously correct and benefits almost all users and applications, at least no regression. No complex configuration or deep knowledge is needed to take advantage of it.
Quoted 4 lines
2. Some way to inspect and control system and application behavior, so that some advanced and customized user space policy daemons can be built to satisfy some advanced users who have the enough knowledge for the applications and systems, for example, oomd.
Agreed, and I think that's the approach that DAMON is currently taking. In specific, we provide DAMON debugfs interface for users who want to inspect and control their system and application behavior. Using it, we also made a PoC level user space policy daemon[1].
For the in-kernel policies, we are developing DAMON-based kernel components one by one, for specific usages. DAMON-based proactive reclamation module (
DAMON_RECLAIM) is one such example. Such DAMON-based components will remove complex tunables that necessary for the general inspection and control of the system but unnecessary for their specific purpose (e.g., proactive reclamation) to allow users use it in a simple manner. Also, those will use conservative default configs to not incur visible regression. For example,DAMON_RECLAIMuses only up to 1% of single CPU time for the reclamation by default.
Quoted 3 lines
In short, I think we're on the same page, and adding DEMOTION scheme action could be helpful for the users who want to efficiently inspect and control the system/application behavior for their tiered memory systems. It's unclear how
Agree. It will be easier for us to deploy it to the products for the common scenarios.
Quoted 2 lines
much benefit this could give to users, though. I assume Baolin would come back with some sort of numbers in the next spin. Nevertheless, I personally don't
Yes, I am still trying to set up the effective measurement environment and get the performance number in the next version.
Quoted 7 lines
think that's a critical blocker, as this patch is essentially just adding a way for using the pre-existing primitive, namely
move_pages(), in a little bit more efficient manner, for the access pattern-based use cases.If I'm missing something, please feel free to let me know.