All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Anderson <seanga2@gmail.com>
To: "hch@infradead.org" <hch@infradead.org>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH blktests] zbd/005: Limit block size to zone length
Date: Sat, 26 Apr 2025 01:23:08 -0400	[thread overview]
Message-ID: <8d8fa127-3bf8-c6b2-71e6-90ce5abcc3df@gmail.com> (raw)
In-Reply-To: <aAuSYhnxwpJns5Cs@infradead.org>

On 4/25/25 09:47, hch@infradead.org wrote:
> On Fri, Apr 25, 2025 at 12:04:39AM -0400, Sean Anderson wrote:
>> and in userspace that assumes 512-byte granularity. But there is no
>> such deeply-ingrained assumption for zones. You just have to set the
>> parameter correctly.
> 
> There are everywhere in software actually using zones.  You still
> haven't answered whay your intended use case is, btw.

I'm working on testing... I thought I would send a few bug fixes upstream in advance...

who knew I would get such a hostile response

>> Plus, smaller zones are more efficient at reducing write amplification,
>> in the same way as smaller block sizes.
> 
> No, they aren't.  If you zones are only a few kb you will waste a lot
> of effort to actually track their state.

The state is perhaps 4-8 bytes at most? And in any case it's proportional to
the number of zones. If you have a smaller drive you will naturally have smaller zones.

--Sean

  reply	other threads:[~2025-04-26  5:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23 16:49 [PATCH blktests] zbd/005: Limit block size to zone length Sean Anderson
2025-04-24  8:09 ` Christoph Hellwig
2025-04-24 11:30   ` Shinichiro Kawasaki
2025-04-24 13:56     ` Sean Anderson
2025-04-24 14:06       ` hch
2025-04-24 14:20         ` Sean Anderson
2025-04-24 14:23           ` hch
2025-04-25  4:04             ` Sean Anderson
2025-04-25 13:47               ` hch
2025-04-26  5:23                 ` Sean Anderson [this message]
2025-04-27  3:23                   ` Keith Busch
2025-04-25  2:37     ` 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=8d8fa127-3bf8-c6b2-71e6-90ce5abcc3df@gmail.com \
    --to=seanga2@gmail.com \
    --cc=hch@infradead.org \
    --cc=linux-block@vger.kernel.org \
    --cc=shinichiro.kawasaki@wdc.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.