linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [LSF/MM TOPIC][ATTEND] stability of vfs level interfaces
Date: Wed, 15 Jan 2014 15:16:45 -0600	[thread overview]
Message-ID: <20140115211645.GQ10553@sgi.com> (raw)

Hi Folks,

I'd like to attend LSF/MM this year.  One subject that I'm interested in
discussing is the stability of vfs level interfaces.  It seems like
there is a lot going on, and that can make things interesting for anyone
who wants to maintain a single filesystem codebase on multiple distros.
e.g. To run a xfs codebase from 3.0 on a 2.6.32 kernel, my count is 28
items to deal with.

If anyone would like to discuss this other than to say "Yeah don't do
that", I'm happy to get the conversation started.

Other topics I'm intersted in:  T10 DIX support, SMR drives, persistent
memory, and offline extents if there is an xfs break-out.

Thanks, 
Ben

                 reply	other threads:[~2014-01-15 21:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20140115211645.GQ10553@sgi.com \
    --to=bpm@sgi.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).