linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: Dave Hansen <dave.hansen@intel.com>
Cc: akpm@linux-foundation.org, aneesh.kumar@kernel.org,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, npiggin@gmail.com, peterz@infradead.org,
	will@kernel.org, david@kernel.org
Subject: Re: [PATCH 1/1] mm/mmu_gather: replace IPI with synchronize_rcu() when batch allocation fails
Date: Tue, 24 Feb 2026 10:06:13 +0800	[thread overview]
Message-ID: <26ffb92e-1e62-4e1a-b31b-465a882c2ec4@linux.dev> (raw)
In-Reply-To: <c348453a-6a1f-43e4-acbb-02bbeb2ce805@intel.com>



On 2026/2/24 00:35, Dave Hansen wrote:
> On 2/23/26 08:29, Lance Yang wrote:
>>
>> Note: Use this when code really needs to wait for synchronization,
>> *not* for freeing memory. Memory freeing should use RCU callbacks
>> that don't cause latency spikes in this thread.
> 
> Yeah, but I'd probably mix it in with the other chit chat about
> non-atomic contexts. I'd also make it something like:
> 
> 	Do not use for freeing memory. Use RCU callbacks instead to
> 	avoid latency spikes.
> 
> to make the commands clear.

Got it, thanks. I'll update it in v2.


      reply	other threads:[~2026-02-24  2:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23  3:36 Lance Yang
2026-02-23  9:29 ` David Hildenbrand (Arm)
2026-02-23 12:58   ` Lance Yang
2026-02-23 13:02     ` David Hildenbrand (Arm)
2026-02-23 15:31     ` Dave Hansen
2026-02-23 16:29       ` Lance Yang
2026-02-23 16:35         ` Dave Hansen
2026-02-24  2:06           ` Lance Yang [this message]

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=26ffb92e-1e62-4e1a-b31b-465a882c2ec4@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@kernel.org \
    --cc=dave.hansen@intel.com \
    --cc=david@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@gmail.com \
    --cc=peterz@infradead.org \
    --cc=will@kernel.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: 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