linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Cc: linux-fsdevel@vger.kernel.org
Subject: [ANNOUNCE] xfs: Supporting Host Aware SMR Drives
Date: Mon, 16 Mar 2015 17:00:20 +1100	[thread overview]
Message-ID: <20150316060020.GB28557@dastard> (raw)

Hi Folks,

As I told many people at Vault last week, I wrote a document
outlining how we should modify the on-disk structures of XFS to
support host aware SMR drives on the (long) plane flights to Boston.

TL;DR: not a lot of change to the XFS kernel code is required, no
specific SMR awareness is needed by the kernel code.  Only
relatively minor tweaks to the on-disk format will be needed and
most of the userspace changes are relatively straight forward, too.

The source for that document can be found in this git tree here:

git://git.kernel.org/pub/scm/fs/xfs/xfs-documentation

in the file design/xfs-smr-structure.asciidoc. Alternatively,
pull it straight from cgit:

https://git.kernel.org/cgit/fs/xfs/xfs-documentation.git/tree/design/xfs-smr-structure.asciidoc

Or there is a pdf version built from the current TOT on the xfs.org
wiki here:

http://xfs.org/index.php/Host_Aware_SMR_architecture

Happy reading!

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

             reply	other threads:[~2015-03-16  6:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-16  6:00 Dave Chinner [this message]
2015-03-16 15:28 ` [ANNOUNCE] xfs: Supporting Host Aware SMR Drives James Bottomley
2015-03-16 18:23   ` Adrian Palmer
2015-03-16 19:06     ` James Bottomley
2015-03-16 20:20       ` Dave Chinner
2015-03-16 22:48         ` Cyril Guyot
2015-03-16 20:32   ` Dave Chinner
2015-03-17  1:12     ` Alireza Haghdoost
2015-03-17  6:06       ` Dave Chinner
2015-03-17 13:25 ` Brian Foster
2015-03-17 21:28   ` Dave Chinner
2015-03-21 14:48     ` Brian Foster

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=20150316060020.GB28557@dastard \
    --to=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /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).