From: Josef Bacik <jbacik@fb.com>
To: <linux-btrfs@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<kernel-team@fb.com>, <jack@suse.com>, <viro@zeniv.linux.org.uk>,
<dchinner@redhat.com>, <hch@lst.de>, <linux-mm@kvack.org>
Subject: [PATCH 0/3][V2] Provide accounting for dirty metadata
Date: Mon, 22 Aug 2016 13:34:59 -0400 [thread overview]
Message-ID: <1471887302-12730-1-git-send-email-jbacik@fb.com> (raw)
Here is my updated set of patches for providing a way for fs'es to do their own
accounting for their dirty metadata pages. The changes since V1 include
-Split the accounting + ->write_metadata patches out into their own patches.
-Added a few more account_metadata* helpers that I hadn't thought about
previously.
-Changed the bdi->sb_list to bdi->dirty_sb_list. This is to avoid confusion
about the purpose of the list. I do a splice of this list when processing it as
we have to drop the list lock and I didn't want to worry about umounts screwing
up the list while we were writing metadata.
-Added the dirty metadata counter to the various places we output those counters
(meminfo, oom messages, etc).
I've also actually changed btrfs to use these interfaces and have been testing
that code for almost a week now and have fixed up the various problems that
happend with V1 of this code. Thanks,
Josef
WARNING: multiple messages have this Message-ID (diff)
From: Josef Bacik <jbacik@fb.com>
To: <linux-btrfs@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<kernel-team@fb.com>, <jack@suse.com>, <viro@zeniv.linux.org.uk>,
<dchinner@redhat.com>, <hch@lst.de>, <linux-mm@kvack.org>
Subject: [PATCH 0/3][V2] Provide accounting for dirty metadata
Date: Mon, 22 Aug 2016 13:34:59 -0400 [thread overview]
Message-ID: <1471887302-12730-1-git-send-email-jbacik@fb.com> (raw)
Here is my updated set of patches for providing a way for fs'es to do their own
accounting for their dirty metadata pages. The changes since V1 include
-Split the accounting + ->write_metadata patches out into their own patches.
-Added a few more account_metadata* helpers that I hadn't thought about
previously.
-Changed the bdi->sb_list to bdi->dirty_sb_list. This is to avoid confusion
about the purpose of the list. I do a splice of this list when processing it as
we have to drop the list lock and I didn't want to worry about umounts screwing
up the list while we were writing metadata.
-Added the dirty metadata counter to the various places we output those counters
(meminfo, oom messages, etc).
I've also actually changed btrfs to use these interfaces and have been testing
that code for almost a week now and have fixed up the various problems that
happend with V1 of this code. Thanks,
Josef
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Josef Bacik <jbacik@fb.com>
To: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kernel-team@fb.com, jack@suse.com, viro@zeniv.linux.org.uk,
dchinner@redhat.com, hch@lst.de, linux-mm@kvack.org
Subject: [PATCH 0/3][V2] Provide accounting for dirty metadata
Date: Mon, 22 Aug 2016 13:34:59 -0400 [thread overview]
Message-ID: <1471887302-12730-1-git-send-email-jbacik@fb.com> (raw)
Here is my updated set of patches for providing a way for fs'es to do their own
accounting for their dirty metadata pages. The changes since V1 include
-Split the accounting + ->write_metadata patches out into their own patches.
-Added a few more account_metadata* helpers that I hadn't thought about
previously.
-Changed the bdi->sb_list to bdi->dirty_sb_list. This is to avoid confusion
about the purpose of the list. I do a splice of this list when processing it as
we have to drop the list lock and I didn't want to worry about umounts screwing
up the list while we were writing metadata.
-Added the dirty metadata counter to the various places we output those counters
(meminfo, oom messages, etc).
I've also actually changed btrfs to use these interfaces and have been testing
that code for almost a week now and have fixed up the various problems that
happend with V1 of this code. Thanks,
Josef
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2016-08-22 17:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 17:34 Josef Bacik [this message]
2016-08-22 17:34 ` [PATCH 0/3][V2] Provide accounting for dirty metadata Josef Bacik
2016-08-22 17:34 ` Josef Bacik
2016-08-22 17:35 ` [PATCH 1/3] remove mapping from balance_dirty_pages*() Josef Bacik
2016-08-22 17:35 ` Josef Bacik
2016-08-22 17:35 ` Josef Bacik
2016-08-22 18:29 ` kbuild test robot
2016-08-22 17:35 ` [PATCH 2/3] writeback: allow for dirty metadata accounting Josef Bacik
2016-08-22 17:35 ` Josef Bacik
2016-08-22 17:35 ` Josef Bacik
2016-09-09 8:17 ` Jan Kara
2016-09-09 8:17 ` Jan Kara
2016-09-12 0:46 ` Dave Chinner
2016-09-12 0:46 ` Dave Chinner
2016-09-12 7:34 ` Jan Kara
2016-09-12 7:34 ` Jan Kara
2016-09-12 14:24 ` Josef Bacik
2016-09-12 14:24 ` Josef Bacik
2016-09-12 14:24 ` Josef Bacik
2016-09-12 23:01 ` Dave Chinner
2016-09-12 23:01 ` Dave Chinner
2016-09-12 14:56 ` Josef Bacik
2016-09-12 14:56 ` Josef Bacik
2016-09-12 14:56 ` Josef Bacik
2016-09-12 23:18 ` Dave Chinner
2016-09-12 23:18 ` Dave Chinner
2016-08-22 17:35 ` [PATCH 3/3] writeback: introduce super_operations->write_metadata Josef Bacik
2016-08-22 17:35 ` Josef Bacik
2016-08-22 17:35 ` Josef Bacik
2016-09-09 8:29 ` Jan Kara
2016-09-09 8:29 ` Jan Kara
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=1471887302-12730-1-git-send-email-jbacik@fb.com \
--to=jbacik@fb.com \
--cc=dchinner@redhat.com \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@zeniv.linux.org.uk \
/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.