Hello, A gentle ping to get your review comments. They will be of great help to me. Explained below that though the compact_memory node is intended for debug purpose, it got other applications too. This patch just aims to improve that by taking help of proactive compaction. Also triggering proactive compaction for every 500msec is not always required (say that I mostly need higher order pages in the systems only at while launching a set of apps, then the work done by the proactive compaction for every 500msec is not going to be useful in other times). Thus users will disable the proactive compaction(sysctl.compaction_proactiveness = 0) and when required can do the out-of-band compaction using the provided interface. If a separate /proc node shouldn't be present just for this, then the other solution I am thinking of is: 1) Trigger the proactive compaction on every write to sysctl.compaction_proactiveness, instead of waiting for 500msec wakeup, thus users can immediately turn on/off the proactive compaction when required. --Thanks On 4/28/2021 9:02 PM, Charan Teja Kalla wrote: > Thanks Mel for your comments!! > > On 4/27/2021 1:39 PM, Mel Gorman wrote: >>> The existing /proc/sys/vm/compact_memory interface do the full node >>> compaction when user writes an arbitrary value to it and is targeted for >>> the usecases like an app launcher prepares the system before the target >>> application runs. >> The intent behind compact_memory was a debugging interface to tell >> the difference between an application failing to allocate a huge page >> prematurely and the inability of compaction to find a free page. >> > > Thanks for clarifying this. > >>> This patch adds a new /proc interface, >>> /proc/sys/vm/proactive_compact_memory, and on write of an arbitrary >>> value triggers the full node compaction but can be stopped in the middle >>> if sufficient higher order(COMPACTION_HPAGE_ORDER) pages available in >>> the system. The availability of pages that a user looking for can be >>> given as input through /proc/sys/vm/compaction_proactiveness. >>> >>> [1]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=facdaa917c4d5a376d09d25865f5a863f906234a >>> >>> Signed-off-by: Charan Teja Reddy <charante@xxxxxxxxxxxxxx> >> Hence, while I do not object to the patch as-such, I'm wary of the trend >> towards improving explicit out-of-band compaction via proc interfaces. I > > I think people relying on this /proc/../compact_memory for reasons of on > demand compaction effects the performance and the kcompactd returns when > even a single page of the order we are looking for is available. Say > that If an app launching completion is relied on the memory > fragmentation, meaning that lesser the system fragmented, lesser it > needs to spend time on allocation as it gets more higher order pages. > With the current compaction methods we may get just one higher order > page at a time (as compaction stops run after that) thus can effect its > launch completion time. The compact_memory node can help in these > situation where the system administrator can defragment system whenever > is required by writing to the compact_node. This is just a theoretical > example. > > Although it is intended for debugging interface, it got a lot of other > applications too. > > This patch aims to improve this interface by taking help from tunables > provided by the proactive compaction. > >> would have preferred if the focus was on reducing the cost of compaction >> so that direct allocation requests succeed quickly or improving background >> compaction via kcompactd when there has been recent failures. > -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project
