linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: Jim Malina <Jim.Malina@wdc.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Albert Chen <Albert.Chen@wdc.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	James Borden <James.Borden@wdc.com>,
	Curtis Stevens <curtis.stevens@wdc.com>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] SMR: Disrupting recording technology meriting a new class of storage device
Date: Thu, 13 Feb 2014 17:18:08 -0500	[thread overview]
Message-ID: <20140213221808.GE11480@thunk.org> (raw)
In-Reply-To: <20140211115739.GD5903@localhost.localdomain>

On Tue, Feb 11, 2014 at 09:57:40AM -0200, Carlos Maiolino wrote:
> 
> Thanks for clarification, and, this just enforce my concept that ZBC protocol
> should be integrated in the generic block layer not make it device-mapper
> dependent. So, make this available to any device that supports it with or
> without the help of DM.

The kernel interface which I have proposed[1] on the linux-fsdevel
list is indeed something that would be integrated in the generic block
device layer.  My hope is that in the near future (I'm waiting for ZBC
prototypes to show up in Mountain View ;-) we will have a patches that
will allow Linux to recognize ZBC drives, and export the ZBC
functionality via the this interface.

[1] http://thread.gmane.org/gmane.linux.file-systems/81970/focus=82309

I also hope that in the near-term future we will have at least one
device-mapper "SMR simulator" which take a standard block device, and
add write-pointer tracking, and then export the same interface.  This
would allow file systems (perhaps btrfs) to experiment with working
with SMR drives, without having to wait for getting a hold of one of
the ZBC drives.  It would also allow people who are interested in
writing a device mapper shim layer which takes a SMR drive, and
exports a host-assisted block device.

Of course, the stacking of the device mapper layers:

	HDD <-> SMR_SIMULATOR <-> SMR_ADAPTER 

is basically a no-op except for introducing performance delays.  But
the idea here is not performance, but allow people to debug their
code.  So the use cases:

	HDD <-> SMR_SIMULATOR <-> SMR_ADAPTER <-> stock linux file system
	HDD <-> SMR_SIMULATOR <-> SMR_ADAPTER <-> ext4 modified to be SMR-friendly
	HDD <-> SMR_SIMULATOR <-> modified btrfs that supports ZBC

would eventually become:

	SMR HDD <-> SMR_ADAPTER <-> stock linux file system
	SMR_HDD <-> SMR_ADAPTER <-> ext4 modified to be SMR-friendly
	SMR_HDD <-> modified btrfs that supports ZBC

And while we wait for SMR_HDD's to become generally available to all
kernel developers, the existence of the device-mapper smr simulator
will enable us to start work on the device-mapper smr adapter, and
file systems that are either modified to be SMR-friendly, or modified
to work directly w/o any adapter layers with SMR drives.

Regards,

						- Ted

      reply	other threads:[~2014-02-13 22:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-01  2:24 [LSF/MM TOPIC] SMR: Disrupting recording technology meriting a new class of storage device Albert Chen
2014-02-07 13:00 ` Carlos Maiolino
2014-02-07 13:46   ` Hannes Reinecke
2014-02-07 17:32     ` Jim Malina
2014-02-11 11:57       ` Carlos Maiolino
2014-02-13 22:18         ` Theodore Ts'o [this message]

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=20140213221808.GE11480@thunk.org \
    --to=tytso@mit.edu \
    --cc=Albert.Chen@wdc.com \
    --cc=James.Borden@wdc.com \
    --cc=Jim.Malina@wdc.com \
    --cc=cmaiolino@redhat.com \
    --cc=curtis.stevens@wdc.com \
    --cc=hare@suse.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@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).