From: Miguel Garrido <miguel@mjgar.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: Chester <somethingsome2000@gmail.com>,
Josef Bacik <josef@redhat.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: What are thoses [btrfs-cache-nnn] kernel threads ?
Date: Fri, 20 May 2011 08:11:13 -0400 [thread overview]
Message-ID: <BANLkTinpF-bW92w5R5z+5SYW_qBjJvyPBw@mail.gmail.com> (raw)
In-Reply-To: <1305890412-sup-1052@shiny>
On Fri, May 20, 2011 at 7:22 AM, Chris Mason <chris.mason@oracle.com> w=
rote:
> Once enabled it does stay on, and strictly speaking it does change th=
e
> disk format. =A0But, it is perfectly safe to go back to a non-space_c=
ache
> enabled kernel and then go back into space cache. =A0Josef set things=
up
> so it would detect a non-space_cache mount and continue properly.
>
> space_cache is wonderful. =A0We did fix up a few bugs in .38 and .39 =
but
> I'll probably have .40 enable it by default.
>
> -chris
>
Sounds good, I thought it just made more sense to have it on by
default if it is that beneficial but I now understand that the option
was introduced to give users a choice until it made sense to enable it
by default.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-05-20 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 2:37 What are thoses [btrfs-cache-nnn] kernel threads ? Christian Robert
2011-05-19 18:26 ` Josef Bacik
2011-05-20 3:13 ` Miguel Garrido
2011-05-20 5:32 ` Chester
2011-05-20 11:22 ` Chris Mason
2011-05-20 12:11 ` Miguel Garrido [this message]
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=BANLkTinpF-bW92w5R5z+5SYW_qBjJvyPBw@mail.gmail.com \
--to=miguel@mjgar.com \
--cc=chris.mason@oracle.com \
--cc=josef@redhat.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=somethingsome2000@gmail.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).