linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Chris Mason <clm@fb.com>
Cc: lsf-pc@lists.linux-foundation.org,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [Lsf-pc] [ATTEND] Filesystem topics
Date: Mon, 5 Jan 2015 11:27:08 +0100	[thread overview]
Message-ID: <20150105102708.GG7056@quack.suse.cz> (raw)
In-Reply-To: <1420228998.13280.0@mail.thefacebook.com>

  Hello,

On Fri 02-01-15 15:03:18, Chris Mason wrote:
> This year at LSF/MM I'd like to talk with everyone about filesystem
> and MM performance in general on mainline kernels.  We're gathering
> more up to date results as we try out 3.18 internally.
  Do you want to have some session on this to gather some feedback on the
data or just a hallway talk will be enough for you?

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2015-01-05 10:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-02 20:03 [ATTEND] Filesystem topics Chris Mason
2015-01-05 10:27 ` Jan Kara [this message]
2015-01-12 14:57   ` [Lsf-pc] " Chris Mason

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=20150105102708.GG7056@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=clm@fb.com \
    --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 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).