From: Nikolay Borisov <nborisov@suse.com>
To: tj@kernel.org
Cc: jbacik@fb.com, jack@suse.cz, jeffm@suse.com,
chandan@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-btrfs@vger.kernel.org, axboe@kernel.dk,
Nikolay Borisov <nborisov@suse.com>
Subject: [RFC PATCH 0/4] Support for metadata specific accounting
Date: Thu, 22 Jun 2017 17:23:20 +0300 [thread overview]
Message-ID: <1498141404-18807-1-git-send-email-nborisov@suse.com> (raw)
Hello,
This series is a report of Josef's original posting [1]. I've included
fine-grained changelog in each patch with my changes. Basically, I've forward
ported it to 4.12-rc6 and tried incorporating the feedback which was given to
every individual patch (I've included link with that information in each
individual patch).
The main rationale of pushing this is to enable btrfs' subpage-blocksizes
patches to eventually be merged.
This patchset depends on patches (in listed order) which have already
been submitted [2] [3] [4]. But overall they don't hamper review.
[1] https://www.spinics.net/lists/linux-btrfs/msg59976.html
[2] https://patchwork.kernel.org/patch/9800129/
[3] https://patchwork.kernel.org/patch/9800985/
[4] https://patchwork.kernel.org/patch/9799735/
Josef Bacik (4):
remove mapping from balance_dirty_pages*()
writeback: convert WB_WRITTEN/WB_DIRITED counters to bytes
writeback: add counters for metadata usage
writeback: introduce super_operations->write_metadata
drivers/base/node.c | 8 ++
drivers/mtd/devices/block2mtd.c | 12 ++-
fs/btrfs/disk-io.c | 6 +-
fs/btrfs/file.c | 3 +-
fs/btrfs/ioctl.c | 3 +-
fs/btrfs/relocation.c | 3 +-
fs/buffer.c | 3 +-
fs/fs-writeback.c | 74 +++++++++++++--
fs/fuse/file.c | 4 +-
fs/iomap.c | 6 +-
fs/ntfs/attrib.c | 10 +-
fs/ntfs/file.c | 4 +-
fs/proc/meminfo.c | 6 ++
fs/super.c | 7 ++
include/linux/backing-dev-defs.h | 8 +-
include/linux/backing-dev.h | 51 +++++++++--
include/linux/fs.h | 4 +
include/linux/mm.h | 9 ++
include/linux/mmzone.h | 3 +
include/linux/writeback.h | 3 +-
include/trace/events/writeback.h | 13 ++-
mm/backing-dev.c | 15 ++-
mm/filemap.c | 4 +-
mm/memory.c | 5 +-
mm/page-writeback.c | 192 ++++++++++++++++++++++++++++++++-------
mm/page_alloc.c | 21 ++++-
mm/util.c | 2 +
mm/vmscan.c | 19 +++-
mm/vmstat.c | 3 +
29 files changed, 418 insertions(+), 83 deletions(-)
--
2.7.4
next reply other threads:[~2017-06-22 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 14:23 Nikolay Borisov [this message]
2017-06-22 14:23 ` [PATCH 1/4] remove mapping from balance_dirty_pages*() Nikolay Borisov
2017-06-22 14:23 ` [PATCH 2/4] writeback: convert WB_WRITTEN/WB_DIRITED counters to bytes Nikolay Borisov
2017-06-22 14:23 ` [PATCH 3/4] writeback: add counters for metadata usage Nikolay Borisov
2017-06-22 14:23 ` [PATCH 4/4] writeback: introduce super_operations->write_metadata Nikolay Borisov
2017-06-22 15:08 ` [RFC PATCH 0/4] Support for metadata specific accounting Josef Bacik
2017-06-23 16:14 ` David Sterba
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=1498141404-18807-1-git-send-email-nborisov@suse.com \
--to=nborisov@suse.com \
--cc=axboe@kernel.dk \
--cc=chandan@linux.vnet.ibm.com \
--cc=jack@suse.cz \
--cc=jbacik@fb.com \
--cc=jeffm@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tj@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 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).