All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: linux-fsdevel@vger.kernel.org, lsf-pc@lists.linux-foundation.org,
	linux-block@vger.kernel.org
Subject: [LSF/MM ATTEND] [LSF/MM TOPIC] Request to attend and for topic of "Block & Filesystem interface"
Date: Fri, 15 Jan 2016 10:54:48 +0000	[thread overview]
Message-ID: <5698CFF8.3010605@redhat.com> (raw)
In-Reply-To: <yq14meiye92.fsf@sermon.lab.mkp.net>

Hi,

I'd like to attend this years LSF/MM and I'd like to propose a reprise 
of the "Block & Filesystem interface" topic that was discussed last 
year. It seemed to generate quite a lot of discussion last time - in 
fact rather more than could easily be squeezed into its timeslot :-) My 
plan for this year would be to do something similar, if it is accepted. 
So just a very few slides summarizing the current situation, whats 
changed since last year, and anything new on the horizon, to help kick 
off the discussion.

I'm also interested in a very wide range of filesytems, storage and mm 
topics, including GFS2, NFS, XFS, ext*, autofs, fedfs, CIFS and 
technologies such as DAX, dedup, compression and encryption,

Steve.

On 12/01/16 16:05, Martin K. Petersen wrote:
> The annual Linux Storage, Filesystem and Memory Management Summit for
> 2016 will be held on April 18th and 19th at the Raleigh Marriott City
> center, Raleigh, NC.
>
> Like last year, LSF/MM will be colocated with the Linux Foundation Vault
> conference which takes place on April 20th and 21st in the same
> venue. For those that do not know, Vault is designed to be an event
> where open source storage and filesystem practitioners meet storage
> implementors and, as such, it would be of benefit for LSF/MM attendees
> to attend.
>
> 	http://events.linuxfoundation.org/events/linux-storage-filesystem-and-mm-summit
> 	http://events.linuxfoundation.org/events/vault
>
> On behalf of the committee I am issuing a call for agenda proposals that
> are suitable for cross-track discussion as well as technical subjects
> for the breakout sessions.
>
> 1) Proposals for agenda topics should be sent before February 29th, 2016
> to:
>
> 	lsf-pc@lists.linux-foundation.org
>
> and cc the Linux list or lists that are relevant for the topic in
> question:
>
> 	ATA:	linux-ide@vger.kernel.org
> 	Block:	linux-block@vger.kernel.org
> 	FS:	linux-fsdevel@vger.kernel.org
> 	MM:	linux-mm@kvack.org
> 	SCSI:	linux-scsi@vger.kernel.org
>
> If advance notice is required for visa applications then please send
> proposals before February 11th. The committee will complete the first
> round of selections near that date to accommodate applications.
>
> Please tag your proposal with [LSF/MM TOPIC] to make it easier to
> track. In addition, please make sure to start a new thread for each
> topic rather than following up to an existing one.
>
> Agenda topics and attendees will be selected by the program committee,
> but the final agenda will be formed by consensus of the attendees at the
> summit.
>
> We will try to cap attendance at around 25-30 per track to facilitate
> discussions, although the final numbers will depend on the room sizes at
> the venue.
>
> 2) Requests to attend the summit should be sent to:
>
> 	lsf-pc@lists.linux-foundation.org
>
> Please summarise what expertise you will bring to the meeting, and what
> you would like to discuss. Please also tag your email with [LSF/MM
> ATTEND] so there is less chance of it getting lost.
>
> Presentations are allowed to guide discussion, but are strongly
> discouraged. There will be no recording or audio bridge. However, we
> expect that written minutes will be published as we did in previous
> years
>
> 2015:
> 	https://lwn.net/Articles/lsfmm2015/
>
> 2014:
> 	http://lwn.net/Articles/LSFMM2014/
>
> 2013:
> 	http://lwn.net/Articles/548089/
>
> 3) If you have feedback on last year's meeting that we can use to
> improve this year's, please also send that to:
>
> 	lsf-pc@lists.linux-foundation.org
>
> Thank you on behalf of the program committee:
>
> Storage:
> 	Jens Axboe (track chair)
> 	James Bottomley
> 	Christoph Hellwig
> 	Martin K. Petersen (program chair)
>
> Filesystems:
> 	Josef Bacik
> 	Jan Kara
> 	Jeff Layton (track chair)
> 	Anna Schumaker
> 	Theodore Ts'o
> 	Ric Wheeler
>
> MM:
> 	Mel Gorman
> 	Johannes Weiner
> 	Rik van Riel (track chair)
>


      parent reply	other threads:[~2016-01-15 10:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12 16:05 LSF/MM 2016: Call for Proposals Martin K. Petersen
2016-01-12 16:05 ` Martin K. Petersen
2016-01-15  8:10 ` [LSF/MM ATTEND] 2016: Requests to attend MM-summit Jesper Dangaard Brouer
2016-01-15  8:10   ` Jesper Dangaard Brouer
2016-01-15 16:49   ` Christoph Lameter
2016-01-15 16:49     ` Christoph Lameter
2016-01-15 10:54 ` Steven Whitehouse [this message]

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=5698CFF8.3010605@redhat.com \
    --to=swhiteho@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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 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.