From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: Petr Mladek <pmladek@suse.com>,
linux-mm@kvack.org,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] mm/page_alloc: Use write_seqlock_irqsave() instead write_seqlock() + local_irq_save().
Date: Fri, 23 Jun 2023 12:11:11 +0200 [thread overview]
Message-ID: <20230623101111.7tuAg5p5@linutronix.de> (raw)
In-Reply-To: <c35ddb2d-c541-d534-24e8-d03d373597d5@I-love.SAKURA.ne.jp>
On 2023-06-23 18:51:24 [+0900], Tetsuo Handa wrote:
> My understanding is that zonelist_iter_begin() accesses only zonelist_update_seq.seqcount .
> From where is the zonelist_update_seq.lock accessed when zonelist_iter_begin() is called?
zonelist_iter_begin()
-> read_seqbegin()
-> read_seqcount_begin()
-> raw_read_seqcount_begin()
-> __read_seqcount_begin()
Now. The inner part looks like
while ((__seq = seqprop_sequence(s)) & 1)
cpu_relax();
but with RT enabled (in-tree, not out-of-tree, in-tree) seqprop_sequence()
goes from:
| __seqprop_##lockname##_sequence(const seqcount_##lockname##_t *s) \
| { \
| unsigned seq = READ_ONCE(s->seqcount.sequence); \
| \
| if (!IS_ENABLED(CONFIG_PREEMPT_RT)) \
| return seq; \
| \
| if (preemptible && unlikely(seq & 1)) { \
| __SEQ_LOCK(lock_acquire); \
| __SEQ_LOCK(lockbase##_unlock(s->lock)); \
| \
| /* \
| * Re-read the sequence counter since the (possibly \
| * preempted) writer made progress. \
| */ \
| seq = READ_ONCE(s->seqcount.sequence); \
| } \
| \
| return seq; \
to
| unsigned __seqprop_spinlock_sequence(const seqcount_spinlock_t *s)
| {
| unsigned seq = READ_ONCE(s->seqcount.sequence);
|
| if (unlikely(seq & 1)) {
| spin_lock(s->lock);
| spin_unlock(s->lock);
| seq = READ_ONCE(s->seqcount.sequence);
| }
| return seq;
| }
tada \o/
Sebastian
next prev parent reply other threads:[~2023-06-23 10:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 10:40 Sebastian Andrzej Siewior
2023-06-21 10:59 ` Michal Hocko
2023-06-21 11:16 ` Sebastian Andrzej Siewior
2023-06-21 11:49 ` Michal Hocko
2023-06-21 13:11 ` Sebastian Andrzej Siewior
2023-06-21 13:22 ` Michal Hocko
2023-06-21 13:25 ` Sebastian Andrzej Siewior
2023-06-21 11:14 ` David Hildenbrand
2023-06-21 11:33 ` Tetsuo Handa
2023-06-21 12:40 ` Petr Mladek
2023-06-21 13:08 ` Sebastian Andrzej Siewior
2023-06-21 13:06 ` Sebastian Andrzej Siewior
2023-06-21 13:32 ` Tetsuo Handa
2023-06-21 14:34 ` Sebastian Andrzej Siewior
2023-06-21 14:50 ` Tetsuo Handa
2023-06-21 23:24 ` Tetsuo Handa
2023-06-22 7:18 ` Michal Hocko
2023-06-22 10:58 ` Tetsuo Handa
2023-06-22 12:09 ` Michal Hocko
2023-06-22 13:36 ` Tetsuo Handa
2023-06-22 14:11 ` Petr Mladek
2023-06-22 14:28 ` Tetsuo Handa
2023-06-23 9:35 ` Sebastian Andrzej Siewior
2023-06-22 15:04 ` Petr Mladek
2023-06-22 15:43 ` Tetsuo Handa
2023-06-23 9:45 ` Sebastian Andrzej Siewior
2023-06-23 9:51 ` Tetsuo Handa
2023-06-23 10:11 ` Sebastian Andrzej Siewior [this message]
2023-06-23 10:36 ` Tetsuo Handa
2023-06-23 12:44 ` Sebastian Andrzej Siewior
2023-06-23 12:57 ` Michal Hocko
2023-06-23 10:53 ` Petr Mladek
2023-06-23 11:16 ` Tetsuo Handa
2023-06-23 13:31 ` Sebastian Andrzej Siewior
2023-06-23 15:38 ` Petr Mladek
2023-06-23 16:04 ` Sebastian Andrzej Siewior
2023-06-23 9:31 ` Sebastian Andrzej Siewior
2023-06-23 7:27 ` Sebastian Andrzej Siewior
2023-06-21 15:38 ` Petr Mladek
2023-06-23 8:12 ` Sebastian Andrzej Siewior
2023-06-23 9:21 ` Michal Hocko
2023-06-23 9:58 ` Sebastian Andrzej Siewior
2023-06-23 10:43 ` Michal Hocko
2023-06-23 10:45 ` Sebastian Andrzej Siewior
2023-06-23 10:50 ` Sebastian Andrzej Siewior
2023-06-23 11:32 ` Michal Hocko
2023-06-23 10:40 ` Petr Mladek
2023-06-23 13:24 ` Sebastian Andrzej Siewior
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=20230623101111.7tuAg5p5@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=lgoncalv@redhat.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.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