LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Hildenbrand <firstname.lastname@example.org>
To: Tiberiu Georgescu <email@example.com>
Cc: Peter Xu <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: Wed, 18 Aug 2021 20:13:47 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
>>> 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.
But I'm not 100% sure what exactly your use case is here and what you
would really need, so you know best :)
>> Very right, maybe we can just avoid tampering with pagemap on shmem completely (which sounds like an excellent idea to me) and document it as "On shared memory, we will never indicate SWAPPED if the pages have been swapped out. Further, PRESENT might be under-indicated: if a shared page is currently not mapped into the page table of a process.". I saw there was a related, proposed doc update, maybe we can finetune that.
> We could take into consideration an alternative approach to retrieving the shared page info in user
> space, like storing it in sys/fs instead of per process. However, just leaving the pagemap functionality
> incomplete, and not providing an alternative to retrieve the missing information, does not seem right. Updating the docs with a "can't do" should be temporary, until an alternative or fix.
As I stated before, making pagemap less broken is not a good idea IMHO.
Either make it really correct or just leave it all broken -- and
document that e.g., other interfaces (lseek) shall be used. It sounds
like they exist and are good enough for CRUI.
And TBH, if other interfaces already exist and get the job done, I'm
more than happy that we can avoid mixing more shmem stuff into pagemap
and trying to compensate performance problems by introducing inconsistency.
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).
> Also, I think you are talking about my own doc update patch. If not, please share a link with your
> next reply.
>  https://marc.info/?m=162878395426774
No, that's it.
David / dhildenb
next prev parent reply other threads:[~2021-08-18 18:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 3:25 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 [this message]
2021-08-19 14:54 ` Tiberiu Georgescu
2021-08-19 17:26 ` David Hildenbrand
2021-08-20 16:49 ` Tiberiu Georgescu
2021-08-20 19:12 ` Peter Xu
2021-08-25 13:40 ` Tiberiu Georgescu
2021-08-25 14:59 ` Peter Xu
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH RFC 0/4] mm: Enable PM_SWAP for shmem with PTE_MARKER' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).