From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
zlang@kernel.org, fstests@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] generic/449: don't run with RT devices
Date: Wed, 21 Feb 2024 17:25:15 +0100 [thread overview]
Message-ID: <20240221162515.GA25439@lst.de> (raw)
In-Reply-To: <20240221155338.GF616564@frogsfrogsfrogs>
On Wed, Feb 21, 2024 at 07:53:38AM -0800, Darrick J. Wong wrote:
> Odd... this test only takes ~50s on my rt testing rig.
>
> _scratch_mkfs_sized should restrict the size of both the data device and
> the rt volume to 256M, right? Looking at tot, it sets "-d size=$fssize"
> and "-r size=$fssize", so I don't think I understand what's going on
> here.
You are right. I have some local patches that messed things up and
increased the data device size based on paramters of the RT device
in _scratch_mkfs_sized. I've fixed this up now.
next prev parent reply other threads:[~2024-02-21 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 6:35 [PATCH] generic/449: don't run with RT devices Christoph Hellwig
2024-02-21 15:53 ` Darrick J. Wong
2024-02-21 16:25 ` Christoph Hellwig [this message]
2024-02-21 17:13 ` Darrick J. Wong
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=20240221162515.GA25439@lst.de \
--to=hch@lst.de \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@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