From: Josef Bacik <josef@toxicpanda.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: "David Sterba" <dsterba@suse.cz>, "Theodore Ts'o" <tytso@mit.edu>,
"Greg KH" <gregkh@linuxfoundation.org>,
"Amir Goldstein" <amir73il@gmail.com>,
"Sasha Levin" <sashal@kernel.org>,
lsf-pc <lsf-pc@lists.linux-foundation.org>,
linux-btrfs@vger.kernel.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
"Jan Kara" <jack@suse.cz>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
"Matthew Wilcox" <willy@infradead.org>,
"Goldwyn Rodrigues" <rgoldwyn@suse.com>,
"Pankaj Raghav" <p.raghav@samsung.com>,
"Javier González" <javier.gonz@samsung.com>,
"Damien Le Moal" <damien.lemoal@opensource.wdc.com>,
"Johannes Thumshirn" <johannes.thumshirn@wdc.com>,
"Chaitanya Kulkarni" <chaitanya.kulkarni@wdc.com>,
"Adam Manzanares" <a.manzanares@samsung.com>,
"kanchan Joshi" <joshi.k@samsung.com>,
"Pankaj Raghav" <pankydev8@gmail.com>,
"Kanchan Joshi" <joshiiitr@gmail.com>
Subject: Re: btrfs profiles to test was: (Re: [LSF/MM TOPIC] FS, MM, and stable trees)
Date: Tue, 15 Mar 2022 10:23:53 -0400 [thread overview]
Message-ID: <YjCheepcDh/oRp9M@localhost.localdomain> (raw)
In-Reply-To: <Yi/FiHhw01zW2NXc@bombadil.infradead.org>
On Mon, Mar 14, 2022 at 03:45:28PM -0700, Luis Chamberlain wrote:
> On Fri, Mar 11, 2022 at 06:07:21PM -0800, Luis Chamberlain wrote:
> > On Thu, Mar 10, 2022 at 01:51:22PM -0500, Josef Bacik wrote:
> > > [root@fedora-rawhide ~]# cat /xfstests-dev/local.config
> > > [btrfs_normal_freespacetree]
> > > [btrfs_compress_freespacetree]
> > > [btrfs_normal]
> > > [btrfs_compression]
> > > [kdave]
> > > [btrfs_normal_noholes]
> > > [btrfs_compress_noholes]
> > > [btrfs_noholes_freespacetree]
> >
> > + linux-btrfs and zone folks.
> >
> > The name needs to be: $FS_$FANCY_SINGLE_SPACED_NAME
>
> Actually using_underscores_is_fine for the hostnames so we can keep
> your original except kdave :) and that just gets mapped to btrfs_kdave
> for now until you guys figure out what to call it.
>
Lol you didn't need to save the name, I just threw that in there because Sterba
wanted me to test something specific for some patch and I just never deleted it.
> Likewise it would be useful if someone goees through these and gives me
> hints as to the kernel revision that supports such config, so that if
> testing on stable for instance or an older kernel, then the kconfig
> option for them does not appear.
>
I'm cloning this stuff and doing it now, I got fed up trying to find the
performance difference between virtme and libvirt. If your shit gives me the
right performance and makes it so I don't have to think then I'll be happy
enough to use it. Thanks,
Josef
next prev parent reply other threads:[~2022-03-15 14:23 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 17:00 [LSF/MM TOPIC] FS, MM, and stable trees Sasha Levin
2019-02-12 21:32 ` Steve French
2019-02-13 7:20 ` Amir Goldstein
2019-02-13 7:37 ` Greg KH
2019-02-13 9:01 ` Amir Goldstein
2019-02-13 9:18 ` Greg KH
2019-02-13 19:25 ` Sasha Levin
2019-02-13 19:52 ` Greg KH
2019-02-13 20:14 ` James Bottomley
2019-02-15 1:50 ` Sasha Levin
2019-02-15 2:48 ` James Bottomley
2019-02-16 18:28 ` Theodore Y. Ts'o
2019-02-21 15:34 ` Luis Chamberlain
2019-02-21 18:52 ` Theodore Y. Ts'o
2019-03-20 3:46 ` Jon Masters
2019-03-20 5:06 ` Greg KH
2019-03-20 6:14 ` Jon Masters
2019-03-20 6:28 ` Greg KH
2019-03-20 6:32 ` Jon Masters
2022-03-08 9:32 ` Amir Goldstein
2022-03-08 10:08 ` Greg KH
2022-03-08 11:04 ` Amir Goldstein
2022-03-08 15:42 ` Luis Chamberlain
2022-03-08 19:06 ` Sasha Levin
2022-03-09 18:57 ` Luis Chamberlain
2022-03-11 5:23 ` Theodore Ts'o
2022-03-11 12:00 ` Jan Kara
2022-03-11 20:52 ` Luis Chamberlain
2022-03-11 22:04 ` Theodore Ts'o
2022-03-11 22:36 ` Luis Chamberlain
2022-04-27 18:58 ` Amir Goldstein
2022-05-01 16:25 ` Luis Chamberlain
2022-03-10 23:59 ` Steve French
2022-03-11 0:36 ` Chuck Lever III
2022-03-11 20:54 ` Luis Chamberlain
2022-03-08 16:40 ` Theodore Ts'o
2022-03-08 17:16 ` Amir Goldstein
2022-03-09 0:43 ` Dave Chinner
2022-03-09 18:41 ` Luis Chamberlain
2022-03-09 18:49 ` Josef Bacik
2022-03-09 19:00 ` Luis Chamberlain
2022-03-09 21:19 ` Josef Bacik
2022-03-10 1:28 ` Luis Chamberlain
2022-03-10 18:51 ` Josef Bacik
2022-03-10 22:41 ` Luis Chamberlain
2022-03-11 12:09 ` Jan Kara
2022-03-11 18:32 ` Luis Chamberlain
2022-03-12 2:07 ` Luis Chamberlain
2022-03-14 22:45 ` btrfs profiles to test was: (Re: [LSF/MM TOPIC] FS, MM, and stable trees) Luis Chamberlain
2022-03-15 14:23 ` Josef Bacik [this message]
2022-03-15 17:42 ` Luis Chamberlain
2022-03-29 20:24 ` [LSF/MM TOPIC] FS, MM, and stable trees Amir Goldstein
2022-04-10 15:11 ` Amir Goldstein
2022-03-08 10:54 ` Jan Kara
2022-03-09 0:02 ` 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=YjCheepcDh/oRp9M@localhost.localdomain \
--to=josef@toxicpanda.com \
--cc=a.manzanares@samsung.com \
--cc=amir73il@gmail.com \
--cc=chaitanya.kulkarni@wdc.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=darrick.wong@oracle.com \
--cc=dsterba@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=javier.gonz@samsung.com \
--cc=johannes.thumshirn@wdc.com \
--cc=joshi.k@samsung.com \
--cc=joshiiitr@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=pankydev8@gmail.com \
--cc=rgoldwyn@suse.com \
--cc=sashal@kernel.org \
--cc=tytso@mit.edu \
--cc=willy@infradead.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