From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Chris Mason <clm@fb.com>
Cc: Dave Chinner <david@fromorbit.com>,
Michal Hocko <mhocko@kernel.org>,
linux-block@vger.kernel.org, linux-mm@kvack.org,
Jerome Glisse <jglisse@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
lsf-pc@lists.linux-foundation.org
Subject: Re: [Lsf-pc] [LSF/MM] schedule suggestion
Date: Thu, 19 Apr 2018 11:07:58 -0400 [thread overview]
Message-ID: <yq1vacnjktt.fsf@oracle.com> (raw)
In-Reply-To: <D8E1F46B-ACC2-4072-A4D1-769A6B4F40F4@fb.com> (Chris Mason's message of "Thu, 19 Apr 2018 10:51:45 -0400")
Chris,
>> I'd like to propose that we compact the fs sessions so that we get a
>> 3-slot session reserved for "Individual filesystem discussions" one
>> afternoon. That way we've got time in the schedule for the all the
>> ext4/btrfs/XFS/NFS/CIFS devs to get together with each other and
>> talk about things of interest only to their own fileystems.
>>
>> That means we all don't have to find time outside the schedule to do
>> this, and think this wold be time very well spent for most fs people
>> at the conf....
>
> I'd love this as well.
Based on feedback last year we explicitly added a third day to LSF/MM to
facilitate hack time and project meetings.
As usual the schedule is fluid and will be adjusted on the fly.
Depending on track, I am hoping we'll be done with the scheduled topics
either at the end of Tuesday or Wednesday morning.
--
Martin K. Petersen Oracle Linux Engineering
_______________________________________________
Lsf-pc mailing list
Lsf-pc@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/lsf-pc
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Chris Mason <clm@fb.com>
Cc: Dave Chinner <david@fromorbit.com>,
Jerome Glisse <jglisse@redhat.com>, <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 11:07:58 -0400 [thread overview]
Message-ID: <yq1vacnjktt.fsf@oracle.com> (raw)
In-Reply-To: <D8E1F46B-ACC2-4072-A4D1-769A6B4F40F4@fb.com> (Chris Mason's message of "Thu, 19 Apr 2018 10:51:45 -0400")
Chris,
>> I'd like to propose that we compact the fs sessions so that we get a
>> 3-slot session reserved for "Individual filesystem discussions" one
>> afternoon. That way we've got time in the schedule for the all the
>> ext4/btrfs/XFS/NFS/CIFS devs to get together with each other and
>> talk about things of interest only to their own fileystems.
>>
>> That means we all don't have to find time outside the schedule to do
>> this, and think this wold be time very well spent for most fs people
>> at the conf....
>
> I'd love this as well.
Based on feedback last year we explicitly added a third day to LSF/MM to
facilitate hack time and project meetings.
As usual the schedule is fluid and will be adjusted on the fly.
Depending on track, I am hoping we'll be done with the scheduled topics
either at the end of Tuesday or Wednesday morning.
--
Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Chris Mason <clm@fb.com>
Cc: Dave Chinner <david@fromorbit.com>,
Jerome Glisse <jglisse@redhat.com>,
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 11:07:58 -0400 [thread overview]
Message-ID: <yq1vacnjktt.fsf@oracle.com> (raw)
In-Reply-To: <D8E1F46B-ACC2-4072-A4D1-769A6B4F40F4@fb.com> (Chris Mason's message of "Thu, 19 Apr 2018 10:51:45 -0400")
Chris,
>> I'd like to propose that we compact the fs sessions so that we get a
>> 3-slot session reserved for "Individual filesystem discussions" one
>> afternoon. That way we've got time in the schedule for the all the
>> ext4/btrfs/XFS/NFS/CIFS devs to get together with each other and
>> talk about things of interest only to their own fileystems.
>>
>> That means we all don't have to find time outside the schedule to do
>> this, and think this wold be time very well spent for most fs people
>> at the conf....
>
> I'd love this as well.
Based on feedback last year we explicitly added a third day to LSF/MM to
facilitate hack time and project meetings.
As usual the schedule is fluid and will be adjusted on the fly.
Depending on track, I am hoping we'll be done with the scheduled topics
either at the end of Tuesday or Wednesday morning.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2018-04-19 15:07 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
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 ` Martin K. Petersen [this message]
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=yq1vacnjktt.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=clm@fb.com \
--cc=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.