From: Nadav Amit <nadav.amit@gmail.com>
To: Nicholas Piggin <npiggin@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Lutomirski <luto@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-arch <linux-arch@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v6 2/5] lazy tlb: allow lazy tlb mm refcounting to be configurable
Date: Mon, 23 Jan 2023 10:02:47 +0200 [thread overview]
Message-ID: <4d26df97-3725-182b-6312-fa5cd8e9f85d@gmail.com> (raw)
In-Reply-To: <ee3844c0-b342-edc6-77cf-4cdc78e30a18@gmail.com>
On 1/23/23 9:35 AM, Nadav Amit wrote:
>> + if (IS_ENABLED(CONFIG_MMU_LAZY_TLB_REFCOUNT)) {
>> + mmdrop(mm);
>> + } else {
>> + /*
>> + * mmdrop_lazy_tlb must provide a full memory barrier, see the
>> + * membarrier comment finish_task_switch which relies on this.
>> + */
>> + smp_mb();
>> + }
>> }
>
> Considering the fact that mmdrop_lazy_tlb() replaced mmdrop() in various
> locations in which smp_mb() was not required, this comment might be
> confusing. IOW, for the cases in most cases where mmdrop_lazy_tlb()
> replaced mmdrop(), this comment was irrelevant, and therefore it now
> becomes confusing.
>
> I am not sure the include the smp_mb() here instead of "open-coding" it
> helps.
I think that I now understand why you do need the smp_mb() here, so
ignore my comment.
next prev parent reply other threads:[~2023-01-23 8:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 8:00 [PATCH v6 0/5] shoot lazy tlbs Nicholas Piggin
2023-01-18 8:00 ` [PATCH v6 1/5] lazy tlb: introduce lazy tlb mm refcount helper functions Nicholas Piggin
2023-01-18 8:00 ` [PATCH v6 2/5] lazy tlb: allow lazy tlb mm refcounting to be configurable Nicholas Piggin
2023-01-23 7:35 ` Nadav Amit
2023-01-23 8:02 ` Nadav Amit [this message]
2023-01-24 2:29 ` Nicholas Piggin
2023-01-18 8:00 ` [PATCH v6 3/5] lazy tlb: shoot lazies, non-refcounting lazy tlb mm reference handling scheme Nicholas Piggin
2023-01-18 22:22 ` Nadav Amit
2023-01-19 0:53 ` Nicholas Piggin
2023-01-19 4:22 ` Nicholas Piggin
2023-01-23 8:16 ` Nadav Amit
2023-01-24 3:16 ` Nicholas Piggin
2023-01-18 8:00 ` [PATCH v6 4/5] powerpc/64s: enable MMU_LAZY_TLB_SHOOTDOWN Nicholas Piggin
2023-01-18 17:30 ` Linus Torvalds
2023-01-19 3:04 ` Nicholas Piggin
2023-01-18 8:00 ` [PATCH v6 5/5] powerpc/64s/radix: combine final TLB flush and lazy tlb mm shootdown IPIs Nicholas Piggin
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=4d26df97-3725-182b-6312-fa5cd8e9f85d@gmail.com \
--to=nadav.amit@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luto@kernel.org \
--cc=npiggin@gmail.com \
--cc=torvalds@linux-foundation.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