From: Christoph Hellwig <hch@lst.de>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Niklas Cassel <cassel@kernel.org>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
Christoph Hellwig <hch@lst.de>,
Benjamin Marzinski <bmarzins@redhat.com>
Subject: Re: [PATCH v4 1/3] block: Improve checks on zone resource limits
Date: Thu, 6 Jun 2024 06:41:22 +0200 [thread overview]
Message-ID: <20240606044122.GB8331@lst.de> (raw)
In-Reply-To: <11c62aed-0048-4420-8edc-a38df761bef2@kernel.org>
On Thu, Jun 06, 2024 at 11:12:08AM +0900, Damien Le Moal wrote:
> Maybe. But that would still not provide any guarantee: a buggy application not
> respecting the limits would be able to steal resources from the other namespace.
>
> In any case, I think this is a discussion to have on the nvme list.
Yes, the per-controller limits in NVMe are a big mistake that was
already mentioned during ZNS standardization. We don't really have
any good way to deal with it except strongly recommending users to
not use multiple ZNS namespaes per controller.
next prev parent reply other threads:[~2024-06-06 4:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 7:51 [PATCH v4 0/3] Fix DM zone resource limits stacking Damien Le Moal
2024-06-05 7:51 ` [PATCH v4 1/3] block: Improve checks on zone resource limits Damien Le Moal
2024-06-05 7:54 ` Christoph Hellwig
2024-06-05 17:25 ` Niklas Cassel
2024-06-06 0:06 ` Damien Le Moal
2024-06-06 1:21 ` Niklas Cassel
2024-06-06 2:12 ` Damien Le Moal
2024-06-06 4:41 ` Christoph Hellwig [this message]
2024-06-05 7:51 ` [PATCH v4 2/3] dm: Improve zone resource limits handling Damien Le Moal
2024-06-05 7:55 ` Christoph Hellwig
2024-06-05 19:47 ` Benjamin Marzinski
2024-06-05 23:52 ` Damien Le Moal
2024-06-06 4:39 ` Christoph Hellwig
2024-06-06 5:48 ` Damien Le Moal
2024-06-05 7:51 ` [PATCH v4 3/3] dm: Remove unused macro DM_ZONE_INVALID_WP_OFST Damien Le Moal
2024-06-05 7:55 ` Christoph Hellwig
2024-06-05 19:50 ` Benjamin Marzinski
2024-06-05 12:40 ` [PATCH v4 0/3] Fix DM zone resource limits stacking Johannes Thumshirn
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=20240606044122.GB8331@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=bmarzins@redhat.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.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).