All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Kanchan Joshi <joshiiitr@gmail.com>, Christoph Hellwig <hch@lst.de>
Cc: Kanchan Joshi <joshi.k@samsung.com>, Jens Axboe <axboe@kernel.dk>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 1/2] nvme: set io-scheduler requirement for ZNS
Date: Wed, 19 Aug 2020 09:38:36 +0000	[thread overview]
Message-ID: <CY4PR04MB375148979AA403CF47EADE0BE75D0@CY4PR04MB3751.namprd04.prod.outlook.com> (raw)
In-Reply-To: CA+1E3rJg0QOX4YgwWJf8Sm=6C-un4TsRX00E31fbFFPT9LYhXg@mail.gmail.com

On 2020/08/19 18:27, Kanchan Joshi wrote:
> On Tue, Aug 18, 2020 at 12:46 PM Christoph Hellwig <hch@lst.de> wrote:
>>
>> On Tue, Aug 18, 2020 at 10:59:35AM +0530, Kanchan Joshi wrote:
>>> Set elevator feature ELEVATOR_F_ZBD_SEQ_WRITE required for ZNS.
>>
>> No, it is not.
> 
> Are you saying MQ-Deadline (write-lock) is not needed for writes on ZNS?
> I see that null-block zoned and SCSI-ZBC both set this requirement. I
> wonder how it became different for NVMe.

It is not required for an NVMe ZNS drive that has zone append native support.
zonefs and upcoming btrfs do not use regular writes, removing the requirement
for zone write locking.

In the context of your patch series, ELEVATOR_F_ZBD_SEQ_WRITE should be set only
and only if the drive does not have native zone append support. And even in that
case, since for an emulated zone append the zone write lock is taken and
released by the emulation driver itself, ELEVATOR_F_ZBD_SEQ_WRITE is required
only if the user will also be issuing regular writes at high QD. And that is
trivially controllable by the user by simply setting the drive elevator to
mq-deadline. Conclusion: setting ELEVATOR_F_ZBD_SEQ_WRITE is not needed.


-- 
Damien Le Moal
Western Digital Research

WARNING: multiple messages have this Message-ID (diff)
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Kanchan Joshi <joshiiitr@gmail.com>, Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
	"sagi@grimberg.me" <sagi@grimberg.me>,
	Kanchan Joshi <joshi.k@samsung.com>,
	Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 1/2] nvme: set io-scheduler requirement for ZNS
Date: Wed, 19 Aug 2020 09:38:36 +0000	[thread overview]
Message-ID: <CY4PR04MB375148979AA403CF47EADE0BE75D0@CY4PR04MB3751.namprd04.prod.outlook.com> (raw)
In-Reply-To: CA+1E3rJg0QOX4YgwWJf8Sm=6C-un4TsRX00E31fbFFPT9LYhXg@mail.gmail.com

On 2020/08/19 18:27, Kanchan Joshi wrote:
> On Tue, Aug 18, 2020 at 12:46 PM Christoph Hellwig <hch@lst.de> wrote:
>>
>> On Tue, Aug 18, 2020 at 10:59:35AM +0530, Kanchan Joshi wrote:
>>> Set elevator feature ELEVATOR_F_ZBD_SEQ_WRITE required for ZNS.
>>
>> No, it is not.
> 
> Are you saying MQ-Deadline (write-lock) is not needed for writes on ZNS?
> I see that null-block zoned and SCSI-ZBC both set this requirement. I
> wonder how it became different for NVMe.

It is not required for an NVMe ZNS drive that has zone append native support.
zonefs and upcoming btrfs do not use regular writes, removing the requirement
for zone write locking.

In the context of your patch series, ELEVATOR_F_ZBD_SEQ_WRITE should be set only
and only if the drive does not have native zone append support. And even in that
case, since for an emulated zone append the zone write lock is taken and
released by the emulation driver itself, ELEVATOR_F_ZBD_SEQ_WRITE is required
only if the user will also be issuing regular writes at high QD. And that is
trivially controllable by the user by simply setting the drive elevator to
mq-deadline. Conclusion: setting ELEVATOR_F_ZBD_SEQ_WRITE is not needed.


-- 
Damien Le Moal
Western Digital Research

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2020-08-19  9:38 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200818053247epcas5p262c5fd7e207dfa5145011c4329cf239d@epcas5p2.samsung.com>
2020-08-18  5:29 ` [PATCH 0/2] enable append-emulation for ZNS Kanchan Joshi
2020-08-18  5:29   ` Kanchan Joshi
     [not found]   ` <CGME20200818053252epcas5p4ee61d64bba5f6a131105e40330984f5e@epcas5p4.samsung.com>
2020-08-18  5:29     ` [PATCH 1/2] nvme: set io-scheduler requirement " Kanchan Joshi
2020-08-18  5:29       ` Kanchan Joshi
2020-08-18  7:11       ` Christoph Hellwig
2020-08-18  7:11         ` Christoph Hellwig
2020-08-19  9:26         ` Kanchan Joshi
2020-08-19  9:26           ` Kanchan Joshi
2020-08-19  9:38           ` Damien Le Moal [this message]
2020-08-19  9:38             ` Damien Le Moal
2020-08-19 10:31             ` Kanchan Joshi
2020-08-19 10:31               ` Kanchan Joshi
2020-08-19 11:17               ` Damien Le Moal
2020-08-19 11:17                 ` Damien Le Moal
2020-09-07  7:00                 ` Kanchan Joshi
2020-09-07  7:00                   ` Kanchan Joshi
2020-09-07  8:22                   ` Damien Le Moal
2020-09-07  8:22                     ` Damien Le Moal
2020-09-07 11:23                     ` Kanchan Joshi
2020-09-07 11:23                       ` Kanchan Joshi
2020-09-07 11:37                       ` Damien Le Moal
2020-09-07 11:37                         ` Damien Le Moal
2020-09-07 11:54                         ` Kanchan Joshi
2020-09-07 11:54                           ` Kanchan Joshi
2020-09-07 12:53                           ` Damien Le Moal
2020-09-07 12:53                             ` Damien Le Moal
     [not found]   ` <CGME20200818053256epcas5p46d0b66b3702192eb6617c8bba334c15f@epcas5p4.samsung.com>
2020-08-18  5:29     ` [PATCH 2/2] nvme: add emulation for zone-append Kanchan Joshi
2020-08-18  5:29       ` Kanchan Joshi
2020-08-18  7:12       ` Christoph Hellwig
2020-08-18  7:12         ` Christoph Hellwig
2020-08-18  9:50         ` Javier Gonzalez
2020-08-18  9:50           ` Javier Gonzalez
2020-08-18 10:51           ` Matias Bjørling
2020-08-18 10:51             ` Matias Bjørling
2020-08-18 18:11             ` Javier Gonzalez
2020-08-18 18:11               ` Javier Gonzalez
2020-08-18 15:50           ` Christoph Hellwig
2020-08-18 15:50             ` Christoph Hellwig
2020-08-18 18:04             ` Javier Gonzalez
2020-08-18 18:04               ` Javier Gonzalez
2020-08-19  7:40               ` Christoph Hellwig
2020-08-19  7:40                 ` Christoph Hellwig
2020-08-19  8:33                 ` Javier Gonzalez
2020-08-19  8:33                   ` Javier Gonzalez
2020-08-19  9:14                   ` Damien Le Moal
2020-08-19  9:14                     ` Damien Le Moal
2020-08-19 10:43                     ` Christoph Hellwig
2020-08-19 10:43                       ` Christoph Hellwig
2020-08-20  6:45                       ` Javier Gonzalez
2020-08-20  6:45                         ` Javier Gonzalez
2020-08-19 10:49                   ` Christoph Hellwig
2020-08-19 10:49                     ` Christoph Hellwig
2020-08-18 16:58           ` Keith Busch
2020-08-18 16:58             ` Keith Busch
2020-08-18 17:29             ` Javier Gonzalez
2020-08-18 17:29               ` Javier Gonzalez
2020-08-18 17:39               ` Keith Busch
2020-08-18 17:39                 ` Keith Busch
2020-08-18 18:13                 ` Javier Gonzalez
2020-08-18 18:13                   ` Javier Gonzalez
2020-08-19 19:11         ` David Fugate
2020-08-19 19:11           ` David Fugate
2020-08-19 19:25           ` Jens Axboe
2020-08-19 19:25             ` Jens Axboe
2020-08-19 21:54             ` David Fugate
2020-08-19 21:54               ` David Fugate
2020-08-19 22:10               ` Keith Busch
2020-08-19 22:10                 ` Keith Busch
2020-08-19 23:43                 ` David Fugate
2020-08-19 23:43                   ` David Fugate
2020-08-20  3:45                   ` Keith Busch
2020-08-20  3:45                     ` Keith Busch
2020-08-20 23:26                     ` David Fugate
2020-08-20 23:26                       ` David Fugate
2020-08-20  5:51                   ` Christoph Hellwig
2020-08-20  5:51                     ` Christoph Hellwig
2020-08-20  6:37             ` Javier Gonzalez
2020-08-20  6:37               ` Javier Gonzalez
2020-08-20  6:52               ` Christoph Hellwig
2020-08-20  6:52                 ` Christoph Hellwig
2020-08-20  8:03                 ` Javier Gonzalez
2020-08-20  8:03                   ` Javier Gonzalez
2020-08-19 21:42           ` Keith Busch
2020-08-19 21:42             ` Keith Busch
2020-08-20  7:37             ` Kanchan Joshi
2020-08-20  7:37               ` Kanchan Joshi
2020-08-20  8:14               ` Javier Gonzalez
2020-08-20  8:14                 ` Javier Gonzalez
2020-08-20  5:29           ` Christoph Hellwig
2020-08-20  5:29             ` Christoph Hellwig

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=CY4PR04MB375148979AA403CF47EADE0BE75D0@CY4PR04MB3751.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=joshi.k@samsung.com \
    --cc=joshiiitr@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.