linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Suren Baghdasaryan <surenb@google.com>,
	Mateusz Guzik <mjguzik@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Liam.Howlett@oracle.com, lstoakes@gmail.com,
	pedro.falcato@gmail.com
Subject: Re: [RFC PATCH] vm: align vma allocation and move the lock back into the struct
Date: Fri, 9 Aug 2024 17:09:14 +0200	[thread overview]
Message-ID: <be0be869-4daf-4530-b90d-6dd6c27c8736@suse.cz> (raw)
In-Reply-To: <CAJuCfpH36sXvCaYL88nzi_8-Yr1tpxHuaLfCMqCac-zN6QHWmg@mail.gmail.com>

On 8/9/24 05:57, Suren Baghdasaryan wrote:
> Maybe it has something to do with NUMA? The system I'm running has 2 NUMA nodes:

I kinda doubt the NUMA aspect. Whether you allocate a vma that embeds a
lock, or a vma and immediately the separate lock, it's unlikely they would
end up on different nodes so from the NUMA perspective I don't see a
difference. And if they ended up on separate nodes, it would more likely be
worse for the case of separate locks, not better.


  parent reply	other threads:[~2024-08-09 15:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08 18:59 Mateusz Guzik
2024-08-08 19:38 ` Suren Baghdasaryan
2024-08-08 20:03   ` Mateusz Guzik
2024-08-08 21:19     ` Suren Baghdasaryan
2024-08-09  3:57       ` Suren Baghdasaryan
2024-08-09  8:14         ` Mateusz Guzik
2024-08-09 14:59           ` Suren Baghdasaryan
2024-08-09 15:09         ` Vlastimil Babka [this message]
2024-08-09 16:56           ` Suren Baghdasaryan
2024-08-11 22:50             ` Suren Baghdasaryan
2024-08-12  4:29               ` Mateusz Guzik
2024-08-12 15:27                 ` Suren Baghdasaryan
2024-08-12 16:30                   ` Mateusz Guzik

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=be0be869-4daf-4530-b90d-6dd6c27c8736@suse.cz \
    --to=vbabka@suse.cz \
    --cc=Liam.Howlett@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lstoakes@gmail.com \
    --cc=mjguzik@gmail.com \
    --cc=pedro.falcato@gmail.com \
    --cc=surenb@google.com \
    /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