From: Chris Mason <clm@fb.com>
To: "Holger Hoffstätte" <holger.hoffstaette@googlemail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/4] btrfs: reduce block group cache writeout times during commit
Date: Thu, 23 Apr 2015 13:57:29 -0400 [thread overview]
Message-ID: <55393289.2040104@fb.com> (raw)
In-Reply-To: <pan.2015.04.23.16.34.05@googlemail.com>
On 04/23/2015 12:34 PM, Holger Hoffstätte wrote:
> kmem_cache_destroy btrfs_transaction: Slab cache still has objects
Josef has a fix for this, but the fix was causing other problems. It's
not a new bug, but we'll get it fixed up.
-chris
next prev parent reply other threads:[~2015-04-23 17:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 19:52 [PATCH 0/4] btrfs: reduce block group cache writeout times during commit Chris Mason
2015-04-13 19:52 ` [PATCH 1/4] btrfs: move struct io_ctl into ctree.h and rename it Chris Mason
2015-04-13 19:52 ` [PATCH 2/4] Btrfs: two stage dirty block group writeout Chris Mason
2015-04-13 19:52 ` [PATCH 3/4] Btrfs: don't use highmem for free space cache pages Chris Mason
2015-04-13 19:52 ` [PATCH 4/4] Btrfs: allow block group cache writeout outside critical section in commit Chris Mason
2015-04-22 16:09 ` [PATCH 0/4] btrfs: reduce block group cache writeout times during commit Lutz Vieweg
2015-04-22 16:37 ` Holger Hoffstätte
2015-04-22 16:55 ` Chris Mason
2015-04-23 12:45 ` Filipe David Manana
2015-04-23 12:52 ` Chris Mason
2015-04-23 12:56 ` Chris Mason
2015-04-23 13:05 ` Filipe David Manana
2015-04-23 15:17 ` Chris Mason
2015-04-23 15:48 ` Filipe David Manana
2015-04-23 19:43 ` Filipe David Manana
2015-04-23 19:50 ` Chris Mason
2015-04-24 6:34 ` Filipe David Manana
2015-04-24 13:00 ` Chris Mason
2015-04-24 13:43 ` Filipe David Manana
2015-04-24 13:55 ` Chris Mason
2015-04-24 15:05 ` Filipe David Manana
2015-04-25 17:33 ` Filipe David Manana
2015-04-24 13:33 ` Chris Mason
2015-04-23 16:34 ` Holger Hoffstätte
2015-04-23 17:57 ` Chris Mason [this message]
2015-06-26 17:12 ` Lutz Vieweg
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=55393289.2040104@fb.com \
--to=clm@fb.com \
--cc=holger.hoffstaette@googlemail.com \
--cc=linux-btrfs@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.