public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org
Subject: [LSF/MM ATTEND] Btrfs subpage-blocksize feature and general filesystem topics
Date: Sun, 31 Jan 2016 07:46:12 +0530	[thread overview]
Message-ID: <3339303.oV3sF53CZb@localhost.localdomain> (raw)

I have been a Btrfs contributor for a little more than 2 years. Apart from
contributing some bug fix patches, I have been mostly working on getting
subpage-blocksize feature (i.e. block size < page size) to work well in
Btrfs.

The most recent posts of the corresponding patchset can be found at,
1. Cleanup patchset
   http://article.gmane.org/gmane.comp.file-systems.btrfs/52394
2. Core patchset
   http://article.gmane.org/gmane.comp.file-systems.btrfs/52408

Very recently the cleanup patchset associated with the subpage-blocksize
feature has been queued for inclusion in Dave Sterba's for-next branch
(http://article.gmane.org/gmane.comp.file-systems.btrfs/52678).

I am interested in attending LSF/MM summit to mostly discuss the future
direction of the subpage-blocksize patchset i.e. The core patchset currently
addresses only regular I/O and also some of the features like Defrag and
Extent cloning. The rest of the features like Scrubbing and Compression need
to be fixed to work in subpage-blocksize scenario. I believe a face-to-face
discussion with other Btrfs developers (to address some of the pain points of
the patchset) would accelerate the process of inclusion of the patchset into
the mainline kernel.

I am also interested in other Btrfs or general filesystem topics.

-- 
chandan


                 reply	other threads:[~2016-01-31  2:17 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=3339303.oV3sF53CZb@localhost.localdomain \
    --to=chandan@linux.vnet.ibm.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