From: Namhyung Kim <namhyung@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>, Will Deacon <will@kernel.org>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.feng@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Byungchul Park <byungchul.park@lge.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, bpf <bpf@vger.kernel.org>,
Radoslaw Burny <rburny@google.com>
Subject: Re: [PATCH 2/4] locking: Apply contention tracepoints in the slow path
Date: Tue, 1 Mar 2022 10:03:57 -0800 [thread overview]
Message-ID: <CAM9d7cguuyY74L9XK=z384bwO6nTCw4XOFNK1yaJhhmKYTBBoA@mail.gmail.com> (raw)
In-Reply-To: <Yh3cwBloddIGvCjU@hirez.programming.kicks-ass.net>
Hi Peter,
On Tue, Mar 1, 2022 at 12:44 AM Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Mon, Feb 28, 2022 at 05:04:10PM -0800, Namhyung Kim wrote:
> > @@ -80,7 +81,9 @@ static inline void queued_read_lock(struct qrwlock *lock)
> > return;
> >
> > /* The slowpath will decrement the reader count, if necessary. */
> > + LOCK_CONTENTION_BEGIN(lock, LCB_F_READ);
> > queued_read_lock_slowpath(lock);
> > + LOCK_CONTENTION_END(lock);
> > }
> >
> > /**
> > @@ -94,7 +97,9 @@ static inline void queued_write_lock(struct qrwlock *lock)
> > if (likely(atomic_try_cmpxchg_acquire(&lock->cnts, &cnts, _QW_LOCKED)))
> > return;
> >
> > + LOCK_CONTENTION_BEGIN(lock, LCB_F_WRITE);
> > queued_write_lock_slowpath(lock);
> > + LOCK_CONTENTION_END(lock);
> > }
>
> > @@ -82,7 +83,9 @@ static __always_inline void queued_spin_lock(struct qspinlock *lock)
> > if (likely(atomic_try_cmpxchg_acquire(&lock->val, &val, _Q_LOCKED_VAL)))
> > return;
> >
> > + LOCK_CONTENTION_BEGIN(lock, 0);
> > queued_spin_lock_slowpath(lock, val);
> > + LOCK_CONTENTION_END(lock);
> > }
>
> Can you please stick that _inside_ the slowpath? You really don't want
> to inline that.
I can move it into the slow path with caller ip.
Thanks,
Namhyung
next prev parent reply other threads:[~2022-03-01 18:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 1:04 [RFC 0/4] locking: Add new lock contention tracepoints (v2) Namhyung Kim
2022-03-01 1:04 ` [PATCH 1/4] locking: Add lock contention tracepoints Namhyung Kim
2022-03-01 1:04 ` [PATCH 2/4] locking: Apply contention tracepoints in the slow path Namhyung Kim
2022-03-01 8:43 ` Peter Zijlstra
2022-03-01 18:03 ` Namhyung Kim [this message]
2022-03-01 9:03 ` Peter Zijlstra
2022-03-01 14:45 ` Steven Rostedt
2022-03-01 18:14 ` Namhyung Kim
2022-03-01 18:11 ` Namhyung Kim
2022-03-14 21:44 ` Namhyung Kim
2022-03-01 1:04 ` [PATCH 3/4] locking/mutex: Pass proper call-site ip Namhyung Kim
2022-03-01 9:05 ` Peter Zijlstra
2022-03-01 14:53 ` Steven Rostedt
2022-03-01 19:47 ` Peter Zijlstra
2022-03-04 7:28 ` Namhyung Kim
2022-03-01 18:25 ` Namhyung Kim
2022-03-01 1:04 ` [PATCH 4/4] locking/rwsem: " Namhyung Kim
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='CAM9d7cguuyY74L9XK=z384bwO6nTCw4XOFNK1yaJhhmKYTBBoA@mail.gmail.com' \
--to=namhyung@kernel.org \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=byungchul.park@lge.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rburny@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).