From: Mike Snitzer <snitzer@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
Mikulas Patocka <mpatocka@redhat.com>, Song Liu <song@kernel.org>,
Yu Kuai <yukuai3@huawei.com>,
dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
linux-raid@vger.kernel.org, lvm-devel@lists.linux.dev
Subject: Re: atomic queue limit updates for stackable devices
Date: Tue, 27 Feb 2024 10:36:37 -0500 [thread overview]
Message-ID: <Zd4BhQ66dC_d7Mn0@redhat.com> (raw)
In-Reply-To: <20240227151734.GA14628@lst.de>
On Tue, Feb 27 2024 at 10:17P -0500,
Christoph Hellwig <hch@lst.de> wrote:
> On Tue, Feb 27, 2024 at 10:16:39AM -0500, Mike Snitzer wrote:
> > That's the mainline issue a bunch of MD (and dm-raid) oriented
> > engineers are working hard to fix, they've been discussing on
> > linux-raid (with many iterations of proposed patches).
> >
> > It regressed due to 6.8 MD changes (maybe earlier).
>
>
> Do you know if there is a way to skip specific tests to get a useful
> baseline value (and to complete the run?)
I only know to sprinkle 'skip' code around to explicitly force the
test to get skipped (e.g. in test/shell/, adding 'skip' at the top of
each test as needed).
But I've cc'd the lvm-devel mailing list in case there is an easier
way.
next parent reply other threads:[~2024-02-27 15:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240223161247.3998821-1-hch@lst.de>
[not found] ` <ZdjXsm9jwQlKpM87@redhat.com>
[not found] ` <ZdjYJrKCLBF8Gw8D@redhat.com>
[not found] ` <20240227151016.GC14335@lst.de>
[not found] ` <Zd38193LQCpF3-D0@redhat.com>
[not found] ` <20240227151734.GA14628@lst.de>
2024-02-27 15:36 ` Mike Snitzer [this message]
2024-02-27 21:50 ` atomic queue limit updates for stackable devices Song Liu
2024-02-28 19:56 ` Christoph Hellwig
2024-02-29 2:02 ` Song Liu
2024-02-29 13:20 ` Christoph Hellwig
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=Zd4BhQ66dC_d7Mn0@redhat.com \
--to=snitzer@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lvm-devel@lists.linux.dev \
--cc=mpatocka@redhat.com \
--cc=song@kernel.org \
--cc=yukuai3@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).