From: David Hildenbrand <david@redhat.com>
To: Michal Hocko <mhocko@suse.com>, Hannes Reinecke <hare@suse.de>
Cc: Oscar Salvador <osalvador@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Hannes Reinecke <hare@kernel.org>
Subject: Re: [RFC] Disable auto_movable_ratio for selfhosted memmap
Date: Mon, 28 Jul 2025 15:08:37 +0200 [thread overview]
Message-ID: <3e88642f-3914-42b0-b864-4ad374b659b5@redhat.com> (raw)
In-Reply-To: <aId16W4EaqjANtKR@tiehlicka>
On 28.07.25 15:06, Michal Hocko wrote:
> On Mon 28-07-25 11:37:46, Hannes Reinecke wrote:
>> On 7/28/25 11:10, David Hildenbrand wrote:
>> And to make matters worse, we have two competing user-space programs:
>> - udev
>> - daxctl
>> neither of which is (or can be made) aware of each other.
>> This leads to races and/or inconsistencies.
>
> Would it help if generic udev memory hotplug rule exclude anything that
> is dax backed? Is there a way to check for that? Sorry if this is a
> stupid question.
Parsing /proc/iomem, it's indicated as "System RAM (kmem)".
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-07-28 13:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 8:15 [RFC] Disable auto_movable_ratio for selfhosted memmap Oscar Salvador
2025-07-28 8:44 ` David Hildenbrand
2025-07-28 9:28 ` Hannes Reinecke
2025-07-28 9:42 ` David Hildenbrand
2025-07-28 8:48 ` Michal Hocko
2025-07-28 8:53 ` David Hildenbrand
2025-07-28 9:04 ` Michal Hocko
2025-07-28 9:10 ` David Hildenbrand
2025-07-28 9:37 ` Hannes Reinecke
2025-07-28 13:06 ` Michal Hocko
2025-07-28 13:08 ` David Hildenbrand [this message]
2025-07-29 7:24 ` Hannes Reinecke
2025-07-29 9:19 ` Michal Hocko
2025-07-29 9:29 ` David Hildenbrand
2025-07-29 9:33 ` Hannes Reinecke
2025-07-29 11:58 ` Michal Hocko
2025-07-29 13:52 ` Hannes Reinecke
2025-07-28 15:15 ` David Hildenbrand
2025-07-28 12:17 ` Michal Hocko
2025-07-28 12:27 ` David Hildenbrand
2025-07-28 12:27 ` David Hildenbrand
2025-07-28 13:00 ` Michal Hocko
2025-07-28 13:03 ` David Hildenbrand
2025-07-28 12:54 ` Michal Hocko
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=3e88642f-3914-42b0-b864-4ad374b659b5@redhat.com \
--to=david@redhat.com \
--cc=hare@kernel.org \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
/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: link
Be 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).