linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, Jun He <jhe@cs.wisc.edu>,
	Peter Desnoyers <pjd@ccs.neu.edu>,
	Abutalib Aghayev <agayev@gmail.com>,
	Daeho Jeong <daeho.jeong@samsung.com>,
	Jin-Soo Kim <jinsookim@skku.edu>,
	Jaegeuk Kim <jaegeuk@kernel.org>,
	Timothy R Feldman <timothy.r.feldman@seagate.com>,
	Adrian Palmer <adrian.palmer@seagate.com>
Subject: Re: Ext4 developers get together planning
Date: Tue, 10 Mar 2015 18:37:20 -0700	[thread overview]
Message-ID: <20150311013720.GD11031@birch.djwong.org> (raw)
In-Reply-To: <nsxbnkb9z0f.fsf@closure.thunk.org>

Are you all set for the ext4 summit?  What is the dial in number for those of
us who cannot make it?

--D

On Mon, Mar 02, 2015 at 10:53:36AM -0500, Theodore Ts'o wrote:
> 
> Looking at the Vault schedule, it looks like the best time to schedule
> the ext4 developer's workshop will be Wednesday from noon to 3pm (we'll
> meet for lunch and then continue until Jan Kara's ext4 file system
> scalaing talk.
> 
> And then we can pick up Thursday morning starting at 10am and go on
> until Lunch.  (Or we could start at 9am and skip the Sasha Levin's file
> system fuzzing talk, but I suspect some people wouldn't want to miss
> Sasha's talk.)
> 
> Does that work for everyone?
> 
> Things which I expect will be on the schedule include:
> 
> * ext4 encryption progress report (Michael Halcrow, Ted)
> * making ext4 smr friendly (Abutalib, Peter, Ted, Tim, Adrian)
> * improving the ext4 block allocator (Jun He)
> 
> Since Jaeguk probably would only be interested in the encryption
> discussions, I'm going to suggest that we schedule the encryption
> discussions for Thursday morning, and the SMR discussions for Wednesday
> afternoon, since our minds will be fresh immediately after the SMR
> discussions on Thursday morning.
> 
> What other topics would people like to include?  Please suggest them on
> this e-mail thread.
> 
> Finally, if you are planning on attending, please send me a private
> e-mail so I know who to expect.  For those of you coming from academia,
> if you haven't already registered for Vault yet, I've recently received
> from Angela on a few compliementary academic registrations, so please
> contact me if you could use one or two.
> 
> Cheers,
> 
>                                                 - Ted
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-03-11  1:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 15:53 Ext4 developers get together planning Theodore Ts'o
2015-03-02 21:20 ` Jan Kara
2015-03-11  1:37 ` Darrick J. Wong [this message]
2015-03-11 13:31   ` Theodore Ts'o

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=20150311013720.GD11031@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=adrian.palmer@seagate.com \
    --cc=agayev@gmail.com \
    --cc=daeho.jeong@samsung.com \
    --cc=jaegeuk@kernel.org \
    --cc=jhe@cs.wisc.edu \
    --cc=jinsookim@skku.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=pjd@ccs.neu.edu \
    --cc=timothy.r.feldman@seagate.com \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).