From: Luis Chamberlain <mcgrof@kernel.org>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Pankaj Raghav <p.raghav@samsung.com>,
Chandan Babu R <chandan.babu@oracle.com>
Subject: Re: xfs kdevops baseline for next-20230725
Date: Thu, 27 Jul 2023 16:01:44 -0700 [thread overview]
Message-ID: <ZML3WJyqSYwzZW0w@bombadil.infradead.org> (raw)
In-Reply-To: <20230727225859.GF11352@frogsfrogsfrogs>
On Thu, Jul 27, 2023 at 03:58:59PM -0700, Darrick J. Wong wrote:
> On Thu, Jul 27, 2023 at 11:21:35AM -0700, Luis Chamberlain wrote:
> > The sections tested for are:
> >
> > xfs_crc
> > xfs_reflink
> > xfs_reflink-normapbt
> > xfs_reflink_1024
> > xfs_reflink_2k
> > xfs_reflink_4k
> > xfs_nocrc
> > xfs_nocrc_512
> > xfs_nocrc_1k
> > xfs_nocrc_2k
> > xfs_nocrc_4k
> > xfs_logdev
> > xfs_rtdev
> > xfs_rtlogdev
>
> Question: Have you turned on gcov to determine how much of fs/xfs/ and
> fs/iomap/ are actually getting exercised by these configurations?
Not yet, and it would somehow have to be the aggregate sum of the
different guests, is that easy to sum up these days, given the same
kernel is used?
> I have for my fstests fleet; it's about ~90% for iomap, ~87% for
> xfs/libxfs, ~84% for the pagecache, and ~80% for xfs/scrub. Was
> wondering what everyone else got on the test.
Neat, it's something we could automate provided if you already have
a way to sum this up, dump it somehwere and we I can make a set of
ansible tasks to do it.
Luis
next prev parent reply other threads:[~2023-07-27 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 18:21 xfs kdevops baseline for next-20230725 Luis Chamberlain
2023-07-27 22:58 ` Darrick J. Wong
2023-07-27 23:01 ` Luis Chamberlain [this message]
2023-07-27 23:06 ` 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=ZML3WJyqSYwzZW0w@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=p.raghav@samsung.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 NNTP newsgroup(s).