All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
	snitzer@kernel.org, mpatocka@redhat.com,
	dm-devel@lists.linux.dev, Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH] dm-delay: support zoned devices
Date: Sun, 23 Mar 2025 07:28:37 +0100	[thread overview]
Message-ID: <20250323062837.GA30617@lst.de> (raw)
In-Reply-To: <Z92naQRO2DrpMnXE@redhat.com>

On Fri, Mar 21, 2025 at 01:52:41PM -0400, Benjamin Marzinski wrote:
> On Fri, Mar 21, 2025 at 08:18:16AM +0100, Christoph Hellwig wrote:
> > Add support for zoned device by passing through report_zoned to the
> > underlying read device.
> > 
> > This is required to make enable xfstests xfs/311 on zoned devices.
> 
> On suspend, delay_presuspend() stops delaying and it doesn't guarantee
> that new bios coming in will always be submitted after the delayed bios
> it is flushing. That can mess things up for zoned devices. I didn't
> check if that matters for the specific test. Setting
> 
> ti->emulate_zone_append = true;
> 
> would enforce write ordering, at the expense of adding a whole other
> layer of delays to zoned dm-delay devices. Since this isn't really
> useful outside of testing, I think that could be acceptable if necessary
> (it would require us to support table reloads of zoned devices with
> emulated zone append, since tests often want to change the delay).
> However it would probably be better to see if we can just make dm-delay
> preserve write ordering during a suspend.

My use case is all about using zone append, so emulating it would be
a bit counter productive, but I'll give it a spin.  I doubt that this
test is very timing critical.


  reply	other threads:[~2025-03-23  6:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21  7:18 [PATCH] dm-delay: support zoned devices Christoph Hellwig
2025-03-21 17:52 ` Benjamin Marzinski
2025-03-23  6:28   ` Christoph Hellwig [this message]
2025-03-26 12:55   ` Damien Le Moal
2025-03-26 15:00     ` Benjamin Marzinski
2025-03-26 15:17       ` Damien Le Moal
2025-03-26 16:57         ` Benjamin Marzinski
2025-03-24 11:09 ` 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=20250323062837.GA30617@lst.de \
    --to=hch@lst.de \
    --cc=bmarzins@redhat.com \
    --cc=dlemoal@kernel.org \
    --cc=dm-devel@lists.linux.dev \
    --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 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.