LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Tiberiu Georgescu <firstname.lastname@example.org> To: David Hildenbrand <email@example.com> Cc: Peter Xu <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, "email@example.com" <firstname.lastname@example.org>, Alistair Popple <email@example.com>, Ivan Teterevkov <firstname.lastname@example.org>, Mike Rapoport <email@example.com>, Hugh Dickins <firstname.lastname@example.org>, Matthew Wilcox <email@example.com>, Andrea Arcangeli <firstname.lastname@example.org>, "Kirill A . Shutemov" <email@example.com>, Andrew Morton <firstname.lastname@example.org>, Mike Kravetz <email@example.com>, "Carl Waldspurger [C]" <firstname.lastname@example.org>, Florian Schmidt <email@example.com>, Jonathan Davies <firstname.lastname@example.org> Subject: Re: [PATCH RFC 0/4] mm: Enable PM_SWAP for shmem with PTE_MARKER Date: Fri, 20 Aug 2021 16:49:58 +0000 [thread overview] Message-ID: <B130B700-B3DB-4D07-A632-73030BCBC715@nutanix.com> (raw) In-Reply-To: <email@example.com> > On 19 Aug 2021, at 18:26, David Hildenbrand <firstname.lastname@example.org> wrote: > > On 19.08.21 16:54, Tiberiu Georgescu wrote: >>> On 18 Aug 2021, at 19:13, David Hildenbrand <email@example.com> wrote: >>> >>>>> >>>>>> I'm now wondering whether for Tiberiu's case mincore() can also be used. It >>>>>> should just still be a bit slow because it'll look up the cache too, but it >>>>>> should work similarly like the original proposal. >>>> I am afraid that the information returned by mincore is a little too vague to be of better help, compared to what the pagemap should provide in theory. I will have a look to see whether lseek on >>>> proc/map_files works as a "PM_SWAP" equivalent. However, the swap offset would still be missing. >>> >>> Well, with mincore() you could at least decide "page is present" vs. "page is swapped or not existent". At least for making pageout decisions it shouldn't really matter, no? madvise(MADV_PAGEOUT) on a hole is a nop. >> I think you are right. In the optimisation we first presented, we should be able to >> send the madvise(MADV_PAGEOUT) call even if the page is none quite safely >> and get the wanted behaviour. Also, the "is_present" or "is_swap_or_none" >> question can be answered by the current pagemap too. Nice catch. >> However, not all use cases are the same. AFAIK, there is still no way to figure >> out whether a shared page is swapped out or none unless it is directly >> read/accessed after a pagemap check. Bringing a page into memory to check >> if it previously was in swap does not seem ideal. > > Well, you can lseek() to remove all the holes and use mincore() to remove all in-memory pages. You're left with the swapped ones. Not the most efficient interface maybe, but there is a way :) Ok, that could work. Still, I have a couple of concerns. Firstly, I am worried lseek with the SEEK_HOLE flag would page in pages from swap, so using it would be a direct factor on its own output. If people are working on Live Migration, this would not be ideal. I am not 100% sure this is how lseek works, so please feel free to contradict me, but I think it would swap in some of the pages that it seeks through, if not all, to figure out when to stop. Unless it leverages the page cache somehow, or an internal bitmap. Secondly, mincore() could return some "false positives" for this particular use case. That is because it returns flag=1 for pages which are still in the swap cache, so the output becomes ambiguous. I am not saying this is not something that would ever be needed. Some people could actually be looking for exactly this scenario, and lseeking during the check could be an advantage. Just that it does not look very flexible. That is why the pagemap would have been ideal for us. Alternatively, to get all logically swapped out pages, the lseek with pagemap should do the trick. As you said, we remove holes with lseek, but we remove in-memory pages with is_present(pte) instead. This solution would still suffer from my first concern, but it should do the job. > >> Also, we still have no mechanism to retrieve the swap offsets of shmem pages >> AFAIK. There is one more QEMU optimisation we are working on that requires >> these mappings available outside of kernel space. > > How exactly would the swap offset really help? IMHO that's a kernel internal that shouldn't be of any value to user space -- it's merely for debugging purposes. But I'd love to learn details. It is possible for the swap device to be network attached and shared, so multiple hosts would need to understand its content. Then it is no longer internal to one kernel only. By being swap-aware, we can skip swapped-out pages during migration (to prevent IO and potential thrashing), and transfer those pages in another way that is zero-copy. > > [...] > >>> If it has an fd and we can punch that into syscalls, we should much rather use that fd to lookup stuff then going via process page tables -- if possible of course (to be evaluated, because I haven't looked into the CRIU details and how they use lseek with anonymous shared memory). >> I found out that it is possible to retrieve the fds of shmem/tmpfs file allocations >> using proc/pid/map_files, which is neat. Still, CRIU does not seem to care >> whether a page is swapped out or just empty, only if it is present on page cache. >> The holes that lseek finds would not be able to infer this difference, AFAIK. Will >> test the behaviour to make sure. > > CRIU wants to migrate everything. lseek() gives you the definitive answer what needs migration -- if it's swapped out or resident. Just skip the holes. Thank you for the summary. I see why the use case is sufficient for CRIU then. In our case, the optimisations aim to make the migration on QEMU swap aware. -- Kind regards, Tibi Georgescu
next prev parent reply other threads:[~2021-08-20 16:50 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-07 3:25 [PATCH RFC 0/4] mm: Enable PM_SWAP for shmem with PTE_MARKER Peter Xu 2021-08-07 3:25 ` [PATCH RFC 1/4] mm: Introduce PTE_MARKER swap entry Peter Xu 2021-08-07 3:25 ` [PATCH RFC 2/4] mm: Check against orig_pte for finish_fault() Peter Xu 2021-08-07 3:25 ` [PATCH RFC 3/4] mm: Handle PTE_MARKER page faults Peter Xu 2021-08-07 3:25 ` [PATCH RFC 4/4] mm: Install marker pte when page out for shmem pages Peter Xu 2021-08-13 15:18 ` Tiberiu Georgescu 2021-08-13 16:01 ` Peter Xu 2021-08-18 18:02 ` Tiberiu Georgescu 2021-08-17 9:04 ` [PATCH RFC 0/4] mm: Enable PM_SWAP for shmem with PTE_MARKER David Hildenbrand 2021-08-17 17:09 ` Peter Xu 2021-08-17 18:46 ` David Hildenbrand 2021-08-17 20:24 ` Peter Xu 2021-08-18 8:24 ` David Hildenbrand 2021-08-18 17:52 ` Tiberiu Georgescu 2021-08-18 18:13 ` David Hildenbrand 2021-08-19 14:54 ` Tiberiu Georgescu 2021-08-19 17:26 ` David Hildenbrand 2021-08-20 16:49 ` Tiberiu Georgescu [this message] 2021-08-20 19:12 ` Peter Xu 2021-08-25 13:40 ` Tiberiu Georgescu 2021-08-25 14:59 ` Peter Xu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=B130B700-B3DB-4D07-A632-73030BCBC715@nutanix.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).