From: Dave Chinner <david@fromorbit.com>
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] common: remove USE_EXTERNAL
Date: Wed, 16 Apr 2025 09:38:37 +1000 [thread overview]
Message-ID: <Z_7t_SKirTrStXEi@dread.disaster.area> (raw)
In-Reply-To: <20250415004452.GO25675@frogsfrogsfrogs>
On Mon, Apr 14, 2025 at 05:44:52PM -0700, Darrick J. Wong wrote:
> On Mon, Apr 14, 2025 at 07:42:05AM +0200, Christoph Hellwig wrote:
> > The USE_EXTERNAL variable indicates that dedicated log or RT devices are
> > in use for the scratch and possibly test device. It gets automatically
> > set when needed and generally does not provide any benefit over simply
> > testing the SCRATCH_LOGDEV and SCRATCH_RTDEV variables.
> >
> > Remove it and replace that test with test for SCRATCH_LOGDEV and
> > SCRATCH_RTDEV, using the more readable if-based syntaxt for all tests
> > touched by this change.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> I like this change, but it leaves me wondering why USE_EXTERNAL even
> exists in the first place? Is that so that you could add
> TEST/SCRATCH_RTDEV to the top of a config file and set
> USE_EXTERNAL={yes,no} as a per-section variable? e.g.
>
> [default]
> TEST_RTDEV=/dev/sde
> SCRATCH_RTDEV=/dev/sdf
>
> [rtstuff]
> USE_EXTERNAL=yes
>
> [simple]
> USE_EXTERNAL=no
Right, that's the way I've been using for a few years, and it is
explicitly the way check-parallel expects external device
enablement in config sections to work....
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2025-04-15 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 5:42 [PATCH] common: remove USE_EXTERNAL Christoph Hellwig
2025-04-15 0:44 ` Darrick J. Wong
2025-04-15 23:38 ` Dave Chinner [this message]
2025-04-15 23:36 ` Dave Chinner
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=Z_7t_SKirTrStXEi@dread.disaster.area \
--to=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--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