From: Peter Zijlstra <peterz@infradead.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
jsquyres@cisco.com, linux-rdma@vger.kernel.org,
general@lists.openfabrics.org, linux-kernel@vger.kernel.org,
Anton Blanchard <anton@samba.org>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [GIT PULL] please pull ummunotify
Date: Thu, 17 Sep 2009 13:30:28 +0200 [thread overview]
Message-ID: <1253187028.8439.2.camel@twins> (raw)
In-Reply-To: <aday6omhz9d.fsf@cisco.com>
On Thu, 2009-09-10 at 21:38 -0700, Roland Dreier wrote:
> Linus, please consider pulling from
>
> master.kernel.org:/pub/scm/linux/kernel/git/roland/infiniband.git ummunotify
>
> This tree is also available from kernel.org mirrors at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/roland/infiniband.git ummunotify
>
> This will get "ummunotify," a new character device that allows a
> userspace library to register for MMU notifications; this is
> particularly useful for MPI implementions (message passing libraries
> used in HPC) to be able to keep track of what wacky things consumers
> do to their memory mappings. My colleague Jeff Squyres from the Open
> MPI project posted a blog entry about why MPI wants this:
>
> http://blogs.cisco.com/ciscotalk/performance/comments/better_linux_memory_tracking/
>
> His summary of ummunotify:
>
> "It’s elegant, doesn’t require strange linker tricks, and seems to
> work in all cases. Yay!"
>
> This code went through several review iterations on lkml and was in
> -mm and -next for quite a few weeks. Andrew is OK with merging it (I
> think -- Andrew please correct me if I misunderstood you).
Anton Blanchard suggested a while back that this might be integrated
with perf-counters, since perf-counters already does mmap() tracking and
also provides events through an mmap()'ed buffer.
Has anybody looked into this?
If someone did and I missed the discussion on why it isn't appropriate,
kindly point me in the right direction ;-)
next prev parent reply other threads:[~2009-09-17 11:30 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 4:38 [GIT PULL] please pull ummunotify Roland Dreier
2009-09-11 5:56 ` KOSAKI Motohiro
2009-09-11 6:03 ` Roland Dreier
2009-09-11 6:11 ` KOSAKI Motohiro
2009-09-11 16:42 ` Gleb Natapov
2009-09-11 6:15 ` Brice Goglin
2009-09-11 6:21 ` KOSAKI Motohiro
2009-09-11 6:22 ` Roland Dreier
2009-09-11 6:40 ` [ofa-general] " Jason Gunthorpe
2009-09-11 16:58 ` Roland Dreier
2009-09-15 7:03 ` KOSAKI Motohiro
2009-09-15 8:27 ` Roland Dreier
2009-09-15 12:38 ` Jeff Squyres
2009-09-15 11:34 ` Pavel Machek
2009-09-15 14:57 ` [ofa-general] " Roland Dreier
2009-09-28 20:49 ` Pavel Machek
2009-09-28 21:40 ` Jason Gunthorpe
2009-09-16 16:30 ` Roland Dreier
2009-09-16 16:40 ` Linus Torvalds
2009-09-17 11:30 ` Peter Zijlstra [this message]
2009-09-17 14:24 ` [ofa-general] " Roland Dreier
2009-09-17 14:32 ` Roland Dreier
2009-09-17 14:49 ` Peter Zijlstra
2009-09-17 15:03 ` Roland Dreier
2009-09-17 15:22 ` Peter Zijlstra
2009-09-17 15:45 ` Roland Dreier
2009-09-18 11:50 ` Ingo Molnar
2009-09-29 17:13 ` Pavel Machek
2009-09-30 9:44 ` Ingo Molnar
2009-09-30 16:02 ` Jason Gunthorpe
2009-10-12 18:19 ` Ingo Molnar
2009-10-12 19:30 ` Jason Gunthorpe
2009-10-12 20:20 ` Ingo Molnar
2009-10-13 4:05 ` Jason Gunthorpe
2009-10-13 6:40 ` Ingo Molnar
2009-10-13 16:27 ` Jason Gunthorpe
2009-10-13 5:43 ` Brice Goglin
2009-10-13 6:38 ` Ingo Molnar
2009-09-30 17:06 ` Roland Dreier
2009-10-02 16:32 ` Roland Dreier
2009-10-02 20:45 ` Pavel Machek
2009-10-07 22:34 ` Roland Dreier
2009-10-12 17:33 ` Peter Zijlstra
2009-09-17 14:43 ` 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=1253187028.8439.2.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=general@lists.openfabrics.org \
--cc=jsquyres@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rdreier@cisco.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