From: Matthew Wilcox <willy@infradead.org>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: Amir Goldstein <amir73il@gmail.com>,
lsf-pc@lists.linux-foundation.org, kdevops@lists.linux.dev,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
linux-cxl@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: Re: kdevops BoF at LSFMM
Date: Mon, 13 May 2024 02:58:09 +0100 [thread overview]
Message-ID: <ZkFzsT1cEztffVa4@casper.infradead.org> (raw)
In-Reply-To: <Zjug3BqYyW3hrMdy@bombadil.infradead.org>
On Wed, May 08, 2024 at 08:57:16AM -0700, Luis Chamberlain wrote:
> It is up to them, I mean, I've started to work on mmtests integration
> so we can help test memory fragmentation, and plan is to integrate
> automation of maple tree and xarray shortly, mm folks are more than
> welcomed!
I don't see how kdevops integration of the radix tree, xarray and maple
tree test suite is useful. It's a white-box test suite. kdevops is
more suited for black-box testing like xfstests and mmtests.
When we find a problem in the various data structures through the black
box testing of their users (like the page cache or the VMA), it's on us
to add tests that exercise that functionality. Like 2a0774c2886d.
The important thing is that the data structures by design don't depend
on much of the kernel. So if they work in-and-of themselves, there's
not much to gain by doing tests in-kernel.
next prev parent reply other threads:[~2024-05-13 1:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 18:44 kdevops BoF at LSFMM Luis Chamberlain
2024-05-07 18:56 ` Chuck Lever III
2024-05-08 7:45 ` Amir Goldstein
2024-05-08 15:57 ` Luis Chamberlain
2024-05-13 1:58 ` Matthew Wilcox [this message]
2024-05-08 17:45 ` Steve French
2024-05-08 17:54 ` Chuck Lever III
2024-05-12 20:20 ` Luis Chamberlain
2024-05-13 13:17 ` Theodore Ts'o
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=ZkFzsT1cEztffVa4@casper.infradead.org \
--to=willy@infradead.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=kdevops@lists.linux.dev \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).