linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org
Subject: [LSF/MM ATTEND] mmap_sem and mm performance testing
Date: Mon, 22 Dec 2014 15:51:24 -0800	[thread overview]
Message-ID: <1419292284.8812.5.camel@stgolabs.net> (raw)

Hello,

I would like to attend LSF/MM 2015. While I am very much interested in
general mm performance topics, I would particularly like to discuss:

(1) Where we are at with the mmap_sem issues and progress. This topic
constantly comes up each year [1,2,3] without much changing. While the
issues are very clear (both long hold times, specially in fs paths and
coarse lock granularity) it would be good to detail exactly *where*
these problems are and what are some of the show stoppers. In addition,
present overall progress and benchmark numbers on fine graining via
range locking (I am currently working on this as a follow on to recent
i_mmap locking patches) and experimental work,
such as speculative page fault patches[4]. If nothing else, this session
can/should produce a list of tangible todo items.

(2) Expanding our mm performance testing. I am working on incorporating
multiple VM-intensive benchmarks taken from system research papers into
mmtests. Academics tend to choose their benchmarking material carefully
and there's no reason we cannot learn from that. The downside is that
their tools are painfully complex to use, and thus not very popular in
the kernel community. Two examples are popular suites such as mosbench
and PARSEC. The idea would be to present easy to use, higher level
benchmarks to expose in-memory scalability issues that be useful to
kernel hackers. Additionally, possibly discuss other tools folks use
that can be beneficial to our internal automation.

[1] http://lwn.net/Articles/490501/
[2] http://lwn.net/Articles/548098/
[3] http://lwn.net/Articles/591978/
[4] http://lwn.net/Articles/617344/

Thanks,
Davidlohr

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

             reply	other threads:[~2014-12-22 23:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-22 23:51 Davidlohr Bueso [this message]
2015-01-02 13:35 ` [Lsf-pc] " Mel Gorman
2015-02-07  2:17   ` Andy Lutomirski

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=1419292284.8812.5.camel@stgolabs.net \
    --to=dave@stgolabs.net \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.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