LWN: Comments on "Moving physical pages from user space" https://lwn.net/Articles/944115/ This is a special feed containing comments posted to the individual LWN article titled "Moving physical pages from user space". en-us Thu, 02 Oct 2025 15:25:32 +0000 Thu, 02 Oct 2025 15:25:32 +0000 https://www.rssboard.org/rss-specification lwn@lwn.net Moving physical pages from user space https://lwn.net/Articles/946101/ https://lwn.net/Articles/946101/ kaesaecracker <div class="FormattedComment"> I think it might make it better, because you could add rules for which process can influence which process and because it would not tell you the physical addresses<br> </div> Mon, 02 Oct 2023 08:40:11 +0000 Moving physical pages from user space https://lwn.net/Articles/945223/ https://lwn.net/Articles/945223/ Aissen <div class="FormattedComment"> I know about CXL, but I fail to see why one would want "profiling mechanisms" to live outside the kernel and move physical pages around. What am I missing ?<br> </div> Thu, 21 Sep 2023 16:46:26 +0000 Moving physical pages from user space https://lwn.net/Articles/944937/ https://lwn.net/Articles/944937/ corbet FWIW, there is <a href="https://lwn.net/ml/linux-kernel/20230919230909.530174-1-gregory.price@memverge.com/">a V2 patch set</a> out there now, without feedback so far. Wed, 20 Sep 2023 07:43:27 +0000 Moving physical pages from user space https://lwn.net/Articles/944914/ https://lwn.net/Articles/944914/ willy <div class="FormattedComment"> For whatever reason, this patch set never made it to the linux-mm mailing list, which may be why it has had so little feedback.<br> <p> It's an ugly design that solves the wrong problem in the wrong way.<br> <p> </div> Tue, 19 Sep 2023 21:54:00 +0000 Moving physical pages from user space https://lwn.net/Articles/944785/ https://lwn.net/Articles/944785/ nim-nim <div class="FormattedComment"> Given that the original motivation is<br> <p> <span class="QuotedText">&gt; For a process executing on a given node, memory attached to that same node will be faster than memory on other nodes, so the placement of memory matters. </span><br> <p> But the proposed implementation is trying to<br> <p> <span class="QuotedText">&gt; move pages between memory types without the need for an awareness of which processes are using those pages.</span><br> <p> I seriously doubt success will be achieved.<br> <p> If user-space detects a fast tier is under utilised but does not want to analyse process by process which one would benefit from a relocation, surely an API prompting the kernel to fill the fast tier, looking itself for the processes that would benefit most would be more appropriate ?<br> <p> <p> </div> Tue, 19 Sep 2023 08:59:09 +0000 Moving physical pages from user space https://lwn.net/Articles/944778/ https://lwn.net/Articles/944778/ florianfainelli <div class="FormattedComment"> Would a system call taking a PID work a bit better, security wise, while still meeting the initial intent?<br> </div> Tue, 19 Sep 2023 02:45:16 +0000 Moving physical pages from user space https://lwn.net/Articles/944776/ https://lwn.net/Articles/944776/ xecycle <div class="FormattedComment"> Seconded. Obtain a pseudo fd and map it, copy over the old page, let the user resolve thread races, then remap over the old address.<br> </div> Tue, 19 Sep 2023 00:47:26 +0000 Moving physical pages from user space https://lwn.net/Articles/944775/ https://lwn.net/Articles/944775/ gerdesj <div class="FormattedComment"> "It seems BPF"<br> <p> I'm just missing "Rust" for bingo. We are at the writing numbers on the table stage now ...<br> </div> Mon, 18 Sep 2023 23:04:14 +0000 Moving physical pages from user space https://lwn.net/Articles/944771/ https://lwn.net/Articles/944771/ ibukanov <div class="FormattedComment"> It seems BPF should be more suitable for this kind of management decision than a user space application.<br> <p> Alternatively, if the app knows so much about physical memory, can kernel just disable virtual memory or at least make it map 1-to-1to physical memory for an app running exclusively on some Numa node?<br> </div> Mon, 18 Sep 2023 20:31:00 +0000 Moving physical pages from user space https://lwn.net/Articles/944768/ https://lwn.net/Articles/944768/ caliloo <div class="FormattedComment"> I wonder what the thinking is when it comes to rights management around such a feature… there also seems to little tangible information about a use case. I’m very curious…<br> </div> Mon, 18 Sep 2023 18:42:45 +0000 Moving physical pages from user space https://lwn.net/Articles/944767/ https://lwn.net/Articles/944767/ alonz Another potential security issue is that moving pages to a slower memory tier can help attackers using timing side channels. Mon, 18 Sep 2023 18:14:36 +0000 Moving physical pages from user space https://lwn.net/Articles/944762/ https://lwn.net/Articles/944762/ quotemstr <div class="FormattedComment"> Why can't the process wanting to migrate the page just mmap it, even use the virtual memory APIs? How does it know what the right PFN even is? This API seems bad.<br> </div> Mon, 18 Sep 2023 15:53:12 +0000 Moving physical pages from user space https://lwn.net/Articles/944761/ https://lwn.net/Articles/944761/ NightMonkey <div class="FormattedComment"> I am confident that there would be many eyes on all patches resulting from this conversation, and my ignorance is vast, but this would seem to open the "attack surface" of the kernel wider. Wouldn't you have to worry more about unauthorized attempts to access memory allocated to other processes? Or devices driver mapped memory?<br> <p> And what about subtle interactions between the mechanisms used for virtual mappings and physical mapping by the kernel? If these subsystems are not "aware" of each other, could new bugs be introduced that would be hard to test for?<br> <p> I'm not saying I believe one path or the other are better, but the security angle seems interesting here.<br> <p> Cheers!<br> </div> Mon, 18 Sep 2023 15:33:44 +0000