From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Christoph Hellwig <hch@lst.de>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Jens Axboe <axboe@kernel.dk>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Keith Busch <Keith.Busch@wdc.com>
Subject: Re: [PATCH v2 0/2] block: add zone write granularity limit
Date: Wed, 20 Jan 2021 10:46:56 +0000 [thread overview]
Message-ID: <BL0PR04MB651400694A65F9FB395C5652E7A20@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20210120100738.GA25746@lst.de
On 2021/01/20 19:07, Christoph Hellwig wrote:
> Shouldn't zonefs (in addition to the pending btrfs and nvmet patches)
> start using this new value instead pf the physical block size?
>
And I think null_blk needs that limit set too. Forgot to add it.
--
Damien Le Moal
Western Digital Research
WARNING: multiple messages have this Message-ID (diff)
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <Keith.Busch@wdc.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2 0/2] block: add zone write granularity limit
Date: Wed, 20 Jan 2021 10:46:56 +0000 [thread overview]
Message-ID: <BL0PR04MB651400694A65F9FB395C5652E7A20@BL0PR04MB6514.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20210120100738.GA25746@lst.de
On 2021/01/20 19:07, Christoph Hellwig wrote:
> Shouldn't zonefs (in addition to the pending btrfs and nvmet patches)
> start using this new value instead pf the physical block size?
>
And I think null_blk needs that limit set too. Forgot to add it.
--
Damien Le Moal
Western Digital Research
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-20 11:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 13:17 [PATCH v2 0/2] block: add zone write granularity limit Damien Le Moal
2021-01-19 13:17 ` Damien Le Moal
2021-01-19 13:17 ` [PATCH v2 1/2] block: introduce zone_write_granularity limit Damien Le Moal
2021-01-19 13:17 ` Damien Le Moal
2021-01-20 10:10 ` Christoph Hellwig
2021-01-20 10:10 ` Christoph Hellwig
2021-01-20 11:00 ` Damien Le Moal
2021-01-20 11:00 ` Damien Le Moal
2021-01-20 12:36 ` Christoph Hellwig
2021-01-20 12:36 ` Christoph Hellwig
2021-01-19 13:17 ` [PATCH v2 2/2] block: document zone_append_max_bytes attribute Damien Le Moal
2021-01-19 13:17 ` Damien Le Moal
2021-01-20 10:10 ` Christoph Hellwig
2021-01-20 10:10 ` Christoph Hellwig
2021-01-20 10:07 ` [PATCH v2 0/2] block: add zone write granularity limit Christoph Hellwig
2021-01-20 10:07 ` Christoph Hellwig
2021-01-20 10:42 ` Damien Le Moal
2021-01-20 10:42 ` Damien Le Moal
2021-01-20 10:46 ` Damien Le Moal [this message]
2021-01-20 10:46 ` Damien Le Moal
-- strict thread matches above, loose matches on Subject: below --
2021-01-19 9:38 Damien Le Moal
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=BL0PR04MB651400694A65F9FB395C5652E7A20@BL0PR04MB6514.namprd04.prod.outlook.com \
--to=damien.lemoal@wdc.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=Keith.Busch@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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.