From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
dm-devel@redhat.com,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-fsdevel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [dm-devel] [PATCH v2 3/3] zonefs: fix synchronous write to sequential zone files
Date: Mon, 19 Apr 2021 08:45:29 +0200 [thread overview]
Message-ID: <20210419064529.GA19041@lst.de> (raw)
In-Reply-To: <20210417023323.852530-4-damien.lemoal@wdc.com>
On Sat, Apr 17, 2021 at 11:33:23AM +0900, Damien Le Moal wrote:
> Synchronous writes to sequential zone files cannot use zone append
> operations if the underlying zoned device queue limit
> max_zone_append_sectors is 0, indicating that the device does not
> support this operation. In this case, fall back to using regular write
> operations.
Zone append is a mandatory feature of the zoned device API.
--
dm-devel mailing list
dm-devel@redhat.com
https://listman.redhat.com/mailman/listinfo/dm-devel
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: dm-devel@redhat.com, Mike Snitzer <snitzer@redhat.com>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-fsdevel@vger.kernel.org,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH v2 3/3] zonefs: fix synchronous write to sequential zone files
Date: Mon, 19 Apr 2021 08:45:29 +0200 [thread overview]
Message-ID: <20210419064529.GA19041@lst.de> (raw)
In-Reply-To: <20210417023323.852530-4-damien.lemoal@wdc.com>
On Sat, Apr 17, 2021 at 11:33:23AM +0900, Damien Le Moal wrote:
> Synchronous writes to sequential zone files cannot use zone append
> operations if the underlying zoned device queue limit
> max_zone_append_sectors is 0, indicating that the device does not
> support this operation. In this case, fall back to using regular write
> operations.
Zone append is a mandatory feature of the zoned device API.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <damien.lemoal@wdc.com>
Cc: dm-devel@redhat.com, Mike Snitzer <snitzer@redhat.com>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-fsdevel@vger.kernel.org,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH v2 3/3] zonefs: fix synchronous write to sequential zone files
Date: Mon, 19 Apr 2021 08:45:29 +0200 [thread overview]
Message-ID: <20210419064529.GA19041@lst.de> (raw)
In-Reply-To: <20210417023323.852530-4-damien.lemoal@wdc.com>
On Sat, Apr 17, 2021 at 11:33:23AM +0900, Damien Le Moal wrote:
> Synchronous writes to sequential zone files cannot use zone append
> operations if the underlying zoned device queue limit
> max_zone_append_sectors is 0, indicating that the device does not
> support this operation. In this case, fall back to using regular write
> operations.
Zone append is a mandatory feature of the zoned device API.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-19 6:45 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 2:33 [dm-devel] [PATCH v2 0/3] Fix dm-crypt zoned block device support Damien Le Moal
2021-04-17 2:33 ` Damien Le Moal
2021-04-17 2:33 ` Damien Le Moal
2021-04-17 2:33 ` [dm-devel] [PATCH v2 1/3] dm: Introduce zone append support control Damien Le Moal
2021-04-17 2:33 ` Damien Le Moal
2021-04-17 2:33 ` Damien Le Moal
2021-04-17 2:33 ` [dm-devel] [PATCH v2 2/3] dm crypt: Fix zoned block device support Damien Le Moal
2021-04-17 2:33 ` Damien Le Moal
2021-04-17 2:33 ` Damien Le Moal
2021-04-17 10:39 ` [dm-devel] " Johannes Thumshirn
2021-04-17 10:39 ` Johannes Thumshirn
2021-04-17 10:39 ` Johannes Thumshirn
2021-04-18 11:00 ` [dm-devel] " Milan Broz
2021-04-18 11:00 ` Milan Broz
2021-04-18 11:00 ` Milan Broz
2021-04-17 2:33 ` [dm-devel] [PATCH v2 3/3] zonefs: fix synchronous write to sequential zone files Damien Le Moal
2021-04-17 2:33 ` Damien Le Moal
2021-04-17 2:33 ` Damien Le Moal
2021-04-19 6:45 ` Christoph Hellwig [this message]
2021-04-19 6:45 ` Christoph Hellwig
2021-04-19 6:45 ` Christoph Hellwig
2021-04-19 7:08 ` [dm-devel] " Damien Le Moal
2021-04-19 7:08 ` Damien Le Moal
2021-04-19 7:08 ` Damien Le Moal
2021-04-19 7:10 ` [dm-devel] " Christoph Hellwig
2021-04-19 7:10 ` Christoph Hellwig
2021-04-19 7:10 ` Christoph Hellwig
2021-04-20 1:20 ` [dm-devel] " Douglas Gilbert
2021-04-20 1:20 ` Douglas Gilbert
2021-04-20 1:20 ` Douglas Gilbert
2021-04-20 1:35 ` [dm-devel] " Damien Le Moal
2021-04-20 1:35 ` Damien Le Moal
2021-04-20 1:35 ` Damien Le Moal
2021-04-19 12:52 ` [dm-devel] [PATCH v2 0/3] Fix dm-crypt zoned block device support Mikulas Patocka
2021-04-19 12:52 ` Mikulas Patocka
2021-04-19 12:52 ` Mikulas Patocka
2021-04-19 13:02 ` Damien Le Moal
2021-04-19 13:02 ` Damien Le Moal
2021-04-19 13:02 ` Damien Le Moal
2021-04-19 13:55 ` Mikulas Patocka
2021-04-19 13:55 ` Mikulas Patocka
2021-04-19 13:55 ` Mikulas Patocka
2021-04-19 14:31 ` Milan Broz
2021-04-19 14:31 ` Milan Broz
2021-04-19 14:31 ` Milan Broz
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=20210419064529.GA19041@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=dm-devel@redhat.com \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=snitzer@redhat.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.