All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Bart Van Assche <bvanassche@acm.org>,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	linux-block@vger.kernel.org
Subject: Re: [blktests] zbd/012: Test requeuing of zoned writes and queue freezing
Date: Wed, 27 Nov 2024 21:21:29 -0800	[thread overview]
Message-ID: <Z0f92dX_0_eQlDbL@infradead.org> (raw)
In-Reply-To: <684a3b59-776a-466a-8323-d92c0502e7a3@kernel.org>

On Thu, Nov 28, 2024 at 02:19:23PM +0900, Damien Le Moal wrote:
> Sounds good. What do you think of adding the opportunistic "update zone wp"
> whenever we execute a user report zones ? It is very easy to do and should not
> slow down significantly report zones itself because we usually have very zone
> write plugs and the hash search is fast.

Just user or any report zones?  But I think updating it is probably a
good thing.  When the zone state is requested there is no excuse to
not have the write plug information in sync


  reply	other threads:[~2024-11-28  5:21 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-25 21:10 [blktests] zbd/012: Test requeuing of zoned writes and queue freezing Bart Van Assche
2024-11-26  8:34 ` Damien Le Moal
2024-11-26 13:44   ` Bart Van Assche
2024-11-27  5:18     ` Damien Le Moal
2024-11-27  6:16       ` Christoph Hellwig
2024-11-27  6:21         ` Christoph Hellwig
2024-11-27  6:32           ` Damien Le Moal
2024-11-27  6:33             ` Christoph Hellwig
2024-11-27  6:43               ` Damien Le Moal
2024-11-27  6:45                 ` Christoph Hellwig
2024-11-27  7:02                   ` Damien Le Moal
2024-11-27  7:19                     ` Christoph Hellwig
2024-11-27  8:17                       ` Damien Le Moal
2024-11-27  8:58                         ` Christoph Hellwig
2024-11-27 11:31                           ` Damien Le Moal
2024-11-27 16:58                             ` Christoph Hellwig
2024-11-27 23:18                               ` Damien Le Moal
2024-11-27 23:36                                 ` Bart Van Assche
2024-11-27 23:43                                   ` Damien Le Moal
2024-11-28  3:20                                 ` Christoph Hellwig
2024-11-28  4:37                                   ` Damien Le Moal
2024-11-28  4:39                                     ` Christoph Hellwig
2024-11-28  4:52                                       ` Damien Le Moal
2024-11-28  5:00                                         ` Christoph Hellwig
2024-11-28  5:07                                           ` Damien Le Moal
2024-11-28  5:16                                             ` Christoph Hellwig
2024-11-28  5:19                                               ` Damien Le Moal
2024-11-28  5:21                                                 ` Christoph Hellwig [this message]
2024-11-28  5:27                                                   ` Damien Le Moal
2024-11-27 17:10           ` Bart Van Assche
2024-11-27 23:11             ` Damien Le Moal
2024-11-26 11:26 ` Damien Le Moal
2024-11-26 12:49   ` Christoph Hellwig
2024-11-27  2:28     ` Damien Le Moal
2024-11-28  4:35 ` Shinichiro Kawasaki

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=Z0f92dX_0_eQlDbL@infradead.org \
    --to=hch@infradead.org \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.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.