All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Damien Le Moal <damien.lemoal@wdc.com>,
	Jens Axboe <axboe@kernel.dk>, <linux-block@vger.kernel.org>,
	<linux-scsi@vger.kernel.org>, Christoph Hellwig <hch@lst.de>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Hannes Reinecke <hare@suse.de>,
	Shaun Tancheff <shaun@tancheff.com>,
	Damien Le Moal <damien.lemoal@hgst.com>
Subject: Re: [PATCH v8 6/7] sd: Implement support for ZBC devices
Date: Tue, 18 Oct 2016 20:44:35 -0400	[thread overview]
Message-ID: <yq1y41lf9qk.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <x498ttlvbks.fsf@segfault.boston.devel.redhat.com> (Jeff Moyer's message of "Tue, 18 Oct 2016 12:58:11 -0400")

>>>>> "Jeff" == Jeff Moyer <jmoyer@redhat.com> writes:

Jeff,

Jeff> Are power of 2 zone sizes required by the standard?  I see why
Jeff> you've done this, but I wonder if we're artificially limiting the
Jeff> implementation, and whether there will be valid devices on the
Jeff> market that simply won't work with Linux because of this.

Standards are deliberately written to be permissive. But Linux doesn't
support arbitrary sector sizes either even though the spec allows it. We
always pick a reasonably sane subset of features to implement and this
case is no different.

After some discussion we decided to rip out all the complexity that was
required to facilitate crazy drive layouts. As a result, the code is now
in a state where we can actually merge it. The hope is that by picking a
specific configuration subset and widely advertising it we can influence
the market.

Also, I am not aware of anybody actually asking the drive vendors to
support crazy zone configurations.

-- 
Martin K. Petersen	Oracle Linux Engineering

WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Damien Le Moal <damien.lemoal@wdc.com>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Hannes Reinecke <hare@suse.de>,
	Shaun Tancheff <shaun@tancheff.com>,
	Damien Le Moal <damien.lemoal@hgst.com>
Subject: Re: [PATCH v8 6/7] sd: Implement support for ZBC devices
Date: Tue, 18 Oct 2016 20:44:35 -0400	[thread overview]
Message-ID: <yq1y41lf9qk.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <x498ttlvbks.fsf@segfault.boston.devel.redhat.com> (Jeff Moyer's message of "Tue, 18 Oct 2016 12:58:11 -0400")

>>>>> "Jeff" == Jeff Moyer <jmoyer@redhat.com> writes:

Jeff,

Jeff> Are power of 2 zone sizes required by the standard?  I see why
Jeff> you've done this, but I wonder if we're artificially limiting the
Jeff> implementation, and whether there will be valid devices on the
Jeff> market that simply won't work with Linux because of this.

Standards are deliberately written to be permissive. But Linux doesn't
support arbitrary sector sizes either even though the spec allows it. We
always pick a reasonably sane subset of features to implement and this
case is no different.

After some discussion we decided to rip out all the complexity that was
required to facilitate crazy drive layouts. As a result, the code is now
in a state where we can actually merge it. The hope is that by picking a
specific configuration subset and widely advertising it we can influence
the market.

Also, I am not aware of anybody actually asking the drive vendors to
support crazy zone configurations.

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2016-10-19  0:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-18  6:40 [PATCH v8 0/7] ZBC / Zoned block device support Damien Le Moal
2016-10-18  6:40 ` Damien Le Moal
2016-10-18  6:40 ` [PATCH v8 1/7] block: Add 'zoned' queue limit Damien Le Moal
2016-10-18  6:40   ` Damien Le Moal
2016-10-18  6:42   ` Hannes Reinecke
2016-10-18  6:42     ` Hannes Reinecke
2016-10-18  6:40 ` [PATCH v8 2/7] blk-sysfs: Add 'chunk_sectors' to sysfs attributes Damien Le Moal
2016-10-18  6:40   ` Damien Le Moal
2016-10-18 16:43   ` Jeff Moyer
2016-10-18 16:43     ` Jeff Moyer
2016-10-18 23:17     ` Damien Le Moal
2016-10-18 23:17       ` Damien Le Moal
2016-10-18  6:40 ` [PATCH v8 3/7] block: update chunk_sectors in blk_stack_limits() Damien Le Moal
2016-10-18  6:40   ` Damien Le Moal
2016-10-18  6:40 ` [PATCH v8 4/7] block: Define zoned block device operations Damien Le Moal
2016-10-18  6:40   ` Damien Le Moal
2016-10-18  6:40 ` [PATCH v8 5/7] block: Implement support for zoned block devices Damien Le Moal
2016-10-18  6:40   ` Damien Le Moal
2016-10-18  6:40 ` [PATCH v8 6/7] sd: Implement support for ZBC devices Damien Le Moal
2016-10-18  6:40   ` Damien Le Moal
2016-10-18 16:58   ` Jeff Moyer
2016-10-18 16:58     ` Jeff Moyer
2016-10-18 18:22     ` Shaun Tancheff
2016-10-18 18:22       ` Shaun Tancheff
2016-10-19 13:23       ` Jeff Moyer
2016-10-19  0:44     ` Martin K. Petersen [this message]
2016-10-19  0:44       ` Martin K. Petersen
2016-10-19 13:21       ` Jeff Moyer
2016-10-19 13:21         ` Jeff Moyer
2016-10-19  0:47   ` Martin K. Petersen
2016-10-19  0:47     ` Martin K. Petersen
2016-10-18  6:40 ` [PATCH v8 7/7] blk-zoned: implement ioctls Damien Le Moal
2016-10-18  6:40   ` Damien Le Moal
2016-10-18 15:58 ` [PATCH v8 0/7] ZBC / Zoned block device support Jens Axboe
2016-10-18 23:15   ` Damien Le Moal
2016-10-18 23:15     ` Damien Le Moal
2016-10-19  0:46   ` Martin K. Petersen
2016-10-19  1:49     ` Jens Axboe
2016-10-19  1:53       ` Martin K. Petersen
2016-10-19  1:59         ` Jens Axboe

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=yq1y41lf9qk.fsf@sermon.lab.mkp.net \
    --to=martin.petersen@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@hgst.com \
    --cc=damien.lemoal@wdc.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jmoyer@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=shaun@tancheff.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.