From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Aaron Lu <aaron.lu@intel.com>
Subject: Re: [RFC PATCH] sched: Fix performance regression introduced by mm_cid
Date: Tue, 4 Apr 2023 09:24:54 -0400 [thread overview]
Message-ID: <e2da64d2-2551-07d8-8905-9a374fdb0591@efficios.com> (raw)
In-Reply-To: <20230404090507.GB284733@hirez.programming.kicks-ass.net>
On 2023-04-04 05:05, Peter Zijlstra wrote:
> On Mon, Apr 03, 2023 at 02:13:42PM -0400, Mathieu Desnoyers wrote:
>> void sched_mm_cid_exit_signals(struct task_struct *t)
>> {
>> struct mm_struct *mm = t->mm;
>> - unsigned long flags;
>> + struct rq_flags rf;
>> + struct rq *rq;
>>
>> if (!mm)
>> return;
>> - local_irq_save(flags);
>> +
>> + preempt_disable();
>> + rq = this_rq();
>> + rq_lock_irqsave(rq, &rf);
>> mm_cid_put(mm, t->mm_cid);
>> - t->mm_cid = -1;
>> + t->last_mm_cid = t->mm_cid = -1;
>> t->mm_cid_active = 0;
>> - local_irq_restore(flags);
>> + rq_unlock_irqrestore(rq, &rf);
>> + preempt_enable();
>> }
>
> FWIW a *slightly* cheaper form is:
>
> preempt_disable();
> rq = this_rq();
> rq_lock_irqsave(rq, &rf);
> preempt_enable_noresched(); /* holding spinlock */
> ...
> rq_unlock_irqrestore(rq, &rf);
Good point, updated for next round.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
https://www.efficios.com
next prev parent reply other threads:[~2023-04-04 13:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 18:13 Mathieu Desnoyers
2023-04-04 0:13 ` Mathieu Desnoyers
2023-04-04 1:59 ` Aaron Lu
2023-04-04 8:57 ` Peter Zijlstra
2023-04-04 9:10 ` Peter Zijlstra
2023-04-04 13:23 ` Mathieu Desnoyers
2023-04-04 9:05 ` Peter Zijlstra
2023-04-04 13:24 ` Mathieu Desnoyers [this message]
2023-04-04 9:21 ` Peter Zijlstra
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=e2da64d2-2551-07d8-8905-9a374fdb0591@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=aaron.lu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®