From: Waiman Long <Waiman.Long@hpe.com>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.com>, Jeff Layton <jlayton@poochiereds.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
Tejun Heo <tj@kernel.org>,
Christoph Lameter <cl@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Andi Kleen <andi@firstfloor.org>,
Dave Chinner <dchinner@redhat.com>,
Scott J Norton <scott.norton@hp.com>,
Douglas Hatch <doug.hatch@hp.com>,
Waiman Long <Waiman.Long@hpe.com>
Subject: [PATCH v2 0/3] vfs: Use per-cpu list for SB's s_inodes list
Date: Fri, 19 Feb 2016 16:10:42 -0500 [thread overview]
Message-ID: <1455916245-32707-1-git-send-email-Waiman.Long@hpe.com> (raw)
v1->v2:
- Use separate structures for list head and nodes & provide a
cleaner interface.
- Use existing list_for_each_entry() or list_for_each_entry_safe()
macros for each of the sb's s_inodes iteration functions instead
of using list_for_each_entry_safe() for all of them which may not
be safe in some cases.
- Use an iterator interface to access all the nodes of a group of
per-cpu lists. This approach is cleaner than the previous double-for
macro which is kind of hacky. However, it does require more lines
of code changes.
- Add a preparatory patch 2 to extract out the per-inode codes from
the superblock s_inodes list iteration functions to minimize code
changes needed in the patch 3.
This patch is a replacement of my previous list batching patch -
https://lwn.net/Articles/674105/. Compared with the previous patch,
this one provides better performance and fairness. However, it also
requires a bit more changes in the VFS layer.
This patchset is a derivative of Andi Kleen's patch on "Initial per
cpu list for the per sb inode list"
https://git.kernel.org/cgit/linux/kernel/git/ak/linux-misc.git/commit/?h=hle315/combined&id=f1cf9e715a40f44086662ae3b29f123cf059cbf4
Patch 1 introduces the per-cpu list.
Patch 2 extracts out the per-inode codes from the superblock s_inodes
list iteration functions to minimize code changes needed in the
following patch.
Patch 3 modifies the superblock and inode structures to use the per-cpu
list. The corresponding functions that reference those structures are
modified.
Waiman Long (3):
lib/percpu-list: Per-cpu list with associated per-cpu locks
vfs: Refactor sb->s_inodes iteration functions
vfs: Use per-cpu list for superblock's inode list
fs/block_dev.c | 71 +++++++++++--------
fs/drop_caches.c | 48 ++++++++-----
fs/fs-writeback.c | 85 ++++++++++++----------
fs/inode.c | 163 ++++++++++++++++++++++++-------------------
fs/notify/inode_mark.c | 145 ++++++++++++++++++++------------------
fs/quota/dquot.c | 134 +++++++++++++++++++++--------------
fs/super.c | 7 +-
include/linux/fs.h | 37 +++++++++-
include/linux/percpu-list.h | 94 +++++++++++++++++++++++++
lib/Makefile | 2 +-
lib/percpu-list.c | 144 ++++++++++++++++++++++++++++++++++++++
11 files changed, 643 insertions(+), 287 deletions(-)
create mode 100644 include/linux/percpu-list.h
create mode 100644 lib/percpu-list.c
next reply other threads:[~2016-02-19 21:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 21:10 Waiman Long [this message]
2016-02-19 21:10 ` [PATCH v2 1/3] lib/percpu-list: Per-cpu list with associated per-cpu locks Waiman Long
2016-02-19 21:10 ` [PATCH v2 2/3] vfs: Refactor sb->s_inodes iteration functions Waiman Long
2016-02-19 21:10 ` [PATCH v2 3/3] vfs: Use per-cpu list for superblock's inode list Waiman Long
2016-02-21 21:34 ` Dave Chinner
2016-02-22 9:18 ` Peter Zijlstra
2016-02-22 11:54 ` Jan Kara
2016-02-22 12:12 ` Peter Zijlstra
2016-02-22 13:04 ` Jan Kara
2016-02-22 21:08 ` Dave Chinner
2016-02-22 22:18 ` Jan Kara
2016-02-23 19:01 ` Waiman Long
2016-02-23 18:56 ` Waiman Long
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=1455916245-32707-1-git-send-email-Waiman.Long@hpe.com \
--to=waiman.long@hpe.com \
--cc=andi@firstfloor.org \
--cc=bfields@fieldses.org \
--cc=cl@linux-foundation.org \
--cc=dchinner@redhat.com \
--cc=doug.hatch@hp.com \
--cc=jack@suse.com \
--cc=jlayton@poochiereds.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--cc=tj@kernel.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 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).