From: Peter Zijlstra <peterz@infradead.org>
To: Axel Rasmussen <axelrasmussen@google.com>
Cc: Michel Lespinasse <walken@google.com>,
David Howells <dhowells@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Jonathan Adams <jwadams@google.com>,
David Rientjes <rientjes@google.com>,
Ying Han <yinghan@google.com>
Subject: Re: [RFC PATCH v3 1/1] mmap_lock: add tracepoints around mmap_lock acquisition
Date: Fri, 19 Jun 2020 10:29:02 +0200 [thread overview]
Message-ID: <20200619082902.GR576905@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20200618222225.102337-2-axelrasmussen@google.com>
On Thu, Jun 18, 2020 at 03:22:25PM -0700, Axel Rasmussen wrote:
>
> include/linux/lockdep.h | 47 ++++++
> include/linux/mmap_lock.h | 27 ++-
> include/linux/rwsem.h | 12 ++
> include/trace/events/mmap_lock.h | 76 +++++++++
> kernel/locking/rwsem.c | 64 +++++++
> mm/Kconfig | 19 +++
> mm/Makefile | 1 +
> mm/mmap_lock.c | 281 +++++++++++++++++++++++++++++++
> 8 files changed, 526 insertions(+), 1 deletion(-)
> create mode 100644 include/trace/events/mmap_lock.h
> create mode 100644 mm/mmap_lock.c
This should have been at least a hand-full of patches. Most definitely
not a single patch.
next prev parent reply other threads:[~2020-06-19 8:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 22:22 [RFC PATCH v3 0/1] Add rwsem "contended hook" API and mmap_lock histograms Axel Rasmussen
2020-06-18 22:22 ` [RFC PATCH v3 1/1] mmap_lock: add tracepoints around mmap_lock acquisition Axel Rasmussen
2020-06-19 8:29 ` Peter Zijlstra [this message]
2020-06-19 8:30 ` Peter Zijlstra
2020-06-19 16:28 ` Axel Rasmussen
2020-06-25 20:25 ` Axel Rasmussen
2020-09-08 11:41 ` Yafang Shao
2020-09-09 16:25 ` Axel Rasmussen
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=20200619082902.GR576905@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=axelrasmussen@google.com \
--cc=dhowells@redhat.com \
--cc=jwadams@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=walken@google.com \
--cc=yinghan@google.com \
/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