From: Dave Chinner <david@fromorbit.com>
To: Jerome Glisse <jglisse@redhat.com>
Cc: linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-block@vger.kernel.org, Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [LSF/MM] schedule suggestion
Date: Thu, 19 Apr 2018 10:48:17 +1000 [thread overview]
Message-ID: <20180419004817.GH27893@dastard> (raw)
In-Reply-To: <20180418211939.GD3476@redhat.com>
On Wed, Apr 18, 2018 at 05:19:39PM -0400, Jerome Glisse wrote:
> Just wanted to suggest to push HMM status down one slot in the
> agenda to avoid having FS and MM first going into their own
> room and then merging back for GUP and DAX, and re-splitting
> after. More over HMM and NUMA talks will be good to have back
> to back as they deal with same kind of thing mostly.
Yeah, I noticed there are a few of these shared sessions that have
been placed in the middle slot of a session. Would be good to put
all the shared fs/mm sessions into a complete session block so
people don't have to keep moving rooms every half hour...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2018-04-19 0:48 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 21:19 [LSF/MM] schedule suggestion Jerome Glisse
2018-04-18 21:19 ` Jerome Glisse
2018-04-19 0:48 ` Dave Chinner [this message]
2018-04-19 1:55 ` [Lsf-pc] " Dave Chinner
2018-04-19 1:55 ` Dave Chinner
2018-04-19 14:38 ` [Lsf-pc] " Jerome Glisse
2018-04-19 14:38 ` Jerome Glisse
2018-04-19 14:38 ` Jerome Glisse
2018-04-19 14:43 ` [Lsf-pc] " Matthew Wilcox
2018-04-19 14:43 ` Matthew Wilcox
2018-04-19 16:30 ` Jerome Glisse
2018-04-19 16:30 ` Jerome Glisse
2018-04-19 16:58 ` [Lsf-pc] " Jeff Layton
2018-04-19 16:58 ` Jeff Layton
2018-04-19 17:26 ` Jerome Glisse
2018-04-19 17:26 ` Jerome Glisse
2018-04-19 18:31 ` [Lsf-pc] " Jeff Layton
2018-04-19 18:31 ` Jeff Layton
2018-04-19 19:31 ` Jerome Glisse
2018-04-19 19:31 ` Jerome Glisse
2018-04-19 19:56 ` [Lsf-pc] " Matthew Wilcox
2018-04-19 19:56 ` Matthew Wilcox
2018-04-19 20:15 ` Jerome Glisse
2018-04-19 20:15 ` Jerome Glisse
2018-04-19 20:25 ` [Lsf-pc] " Matthew Wilcox
2018-04-19 20:25 ` Matthew Wilcox
2018-04-19 20:39 ` [Lsf-pc] " Al Viro
2018-04-19 20:39 ` Al Viro
2018-04-19 21:08 ` Jerome Glisse
2018-04-19 21:08 ` Jerome Glisse
2018-04-19 20:51 ` [Lsf-pc] " Al Viro
2018-04-19 20:51 ` Al Viro
2018-04-19 20:33 ` [Lsf-pc] " Al Viro
2018-04-19 20:33 ` Al Viro
2018-04-19 20:58 ` Jerome Glisse
2018-04-19 20:58 ` Jerome Glisse
2018-04-19 21:21 ` [Lsf-pc] " Al Viro
2018-04-19 21:21 ` Al Viro
2018-04-19 21:47 ` Jerome Glisse
2018-04-19 21:47 ` Jerome Glisse
2018-04-19 22:13 ` [Lsf-pc] " Al Viro
2018-04-19 22:13 ` Al Viro
2018-04-19 14:51 ` [Lsf-pc] " Chris Mason
2018-04-19 14:51 ` Chris Mason
2018-04-19 14:51 ` Chris Mason
2018-04-19 15:07 ` [Lsf-pc] " Martin K. Petersen
2018-04-19 15:07 ` Martin K. Petersen
2018-04-19 15:07 ` Martin K. Petersen
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=20180419004817.GH27893@dastard \
--to=david@fromorbit.com \
--cc=hannes@cmpxchg.org \
--cc=jglisse@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mhocko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.