The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Davidlohr Bueso <dave@stgolabs.net>
To: Waiman Long <longman@redhat.com>
Cc: 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>,
	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>,
	Boqun Feng <boqun.feng@gmail.com>
Subject: Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list
Date: Wed, 29 Nov 2017 07:26:02 -0800	[thread overview]
Message-ID: <20171129152602.p4dzxhoaruza47ol@linux-n805> (raw)
In-Reply-To: <1509475860-16139-1-git-send-email-longman@redhat.com>

Are you planning on sending a v9 with the discussed changes? afaict:

- Drop last two patches
- Fix tearing (WRITE/READ_ONCE())
- Reduce barrier usage for dlock_lists_empty() -- which I'll be sending
  you shortly.

Thanks,
Davidlohr

On Tue, 31 Oct 2017, Waiman Long wrote:

>v7->v8:
> - Integrate the additional patches 8, 9 and 10 sent to fix issues in
>   the original v7 patchset into patch 1 and adjust the other patches
>   accordingly.
>
>v6->v7:
> - Fix outdated email address.
> - Add a comment to patch 4 to explain allocation issue & fix a
>   compilation problem with cpumask.
> - Replace patch 6 with another one that adds an irqsafe mode argument
>   in alloc_dlock_list_heads() instead of adding new APIs.
>
>v5->v6:
> - Rebased the patch to 4.14-rc3.
> - Drop the fsnotify patch as it had been merged somehow.
> - Add a new patch 5 with alternative way of selecting list by hashing
>   instead of cpu #.
> - Add a new patch 6 to proivde a set irq safe APIs to be used in
>   interrupt context.
> - Update the CPU to index mapping code.
>
>v4->v5:
> - Rebased the patch to 4.8-rc1 (changes to fs/fs-writeback.c was
>   dropped).
> - Use kcalloc() instead of percpu_alloc() to allocate the dlock list
>   heads structure as suggested by Christoph Lameter.
> - Replaced patch 5 by another one that made sibling CPUs use the same
>   dlock list head thus reducing the number of list heads that needed
>   to be maintained.
>
>v3->v4:
> - As suggested by Al, encapsulate the dlock list mechanism into
>   the dlist_for_each_entry() and dlist_for_each_entry_safe()
>   which are the equivalent of list_for_each_entry() and
>   list_for_each_entry_safe() for regular linked list. That simplifies
>   the changes in the call sites that perform dlock list iterations.
> - Add a new patch to make the percpu head structure cacheline aligned
>   to prevent cacheline contention from disrupting the performance
>   of nearby percpu variables.
>
>v2->v3:
> - Remove the 2 persubnode API patches.
> - Merge __percpu tag patch 2 into patch 1.
> - As suggested by Tejun Heo, restructure the dlock_list_head data
>   structure to hide the __percpu tag and rename some of the functions
>   and structures.
> - Move most of the code from dlock_list.h to dlock_list.c and export
>   the symbols.
>
>v1->v2:
> - Add a set of simple per-subnode APIs that is between percpu and
>   per-node in granularity.
> - Make dlock list to use the per-subnode APIs so as to reduce the
>   total number of separate linked list that needs to be managed
>   and iterated.
> - There is no change in patches 1-5.
>
>This patchset provides new APIs for a set of distributed locked lists
>(one/CPU core) to minimize lock and cacheline contention. Insertion
>and deletion to the list will be cheap and relatively contention free.
>Lookup, on the other hand, may be a bit more costly as there are
>multiple lists to iterate. This is not really a problem for the
>replacement of superblock's inode list by dlock list included in
>the patchset as lookup isn't needed.
>
>For use cases that need to do lookup, the dlock list can also be
>treated as a set of hashed lists that scales with the number of CPU
>cores in the system.
>
>Both patches 5 and 6 are added to support other use cases like epoll
>nested callbacks, for example, which could use the dlock-list to
>reduce lock contention problem.
>
>Patch 1 introduces the dlock list. The list heads are allocated
>by kcalloc() instead of percpu_alloc(). Each list head entry is
>cacheline aligned to minimize contention.
>
>Patch 2 replaces the use of list_for_each_entry_safe() in
>evict_inodes() and invalidate_inodes() by list_for_each_entry().
>
>Patch 3 modifies the superblock and inode structures to use the dlock
>list. The corresponding functions that reference those structures
>are modified.
>
>Patch 4 makes the sibling CPUs use the same dlock list head to reduce
>the number of list heads that need to be iterated.
>
>Patch 5 enables alternative use case of as a set of hashed lists.
>
>Patch 6 provides an irq safe mode specified at dlock-list allocation
>time so that it can be used within interrupt context.
>
>Jan Kara (1):
>  vfs: Remove unnecessary list_for_each_entry_safe() variants
>
>Waiman Long (5):
>  lib/dlock-list: Distributed and lock-protected lists
>  vfs: Use dlock list for superblock's inode list
>  lib/dlock-list: Make sibling CPUs share the same linked list
>  lib/dlock-list: Enable faster lookup with hashing
>  lib/dlock-list: Add an IRQ-safe mode to be used in interrupt handler
>
> fs/block_dev.c             |   9 +-
> fs/drop_caches.c           |   9 +-
> fs/inode.c                 |  38 ++----
> fs/notify/fsnotify.c       |   9 +-
> fs/quota/dquot.c           |  14 +-
> fs/super.c                 |   7 +-
> include/linux/dlock-list.h | 263 +++++++++++++++++++++++++++++++++++
> include/linux/fs.h         |   8 +-
> lib/Makefile               |   2 +-
> lib/dlock-list.c           | 333 +++++++++++++++++++++++++++++++++++++++++++++
> 10 files changed, 638 insertions(+), 54 deletions(-)
> create mode 100644 include/linux/dlock-list.h
> create mode 100644 lib/dlock-list.c
>
>-- 
>1.8.3.1
>

  parent reply	other threads:[~2017-11-29 15:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 18:50 [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list Waiman Long
2017-10-31 18:50 ` [PATCH v8 1/6] lib/dlock-list: Distributed and lock-protected lists Waiman Long
2017-10-31 21:37   ` Davidlohr Bueso
2017-11-01 18:44     ` Waiman Long
2017-11-02 17:04   ` Davidlohr Bueso
2017-11-02 17:30     ` Waiman Long
2017-11-03 13:34       ` Davidlohr Bueso
2017-11-03 14:22         ` [PATCH v3] lib/dlock-list: Scale dlock_lists_empty() Davidlohr Bueso
2017-11-03 16:33           ` Waiman Long
2017-11-06 18:47             ` [PATCH v4] " Davidlohr Bueso
2017-11-06 19:06               ` Waiman Long
2017-11-07 11:59               ` Jan Kara
2017-11-07 17:59                 ` Andreas Dilger
2017-11-07 18:57                   ` Waiman Long
2017-11-07 19:36                     ` James Bottomley
2017-11-08  2:08                   ` Boqun Feng
2017-11-09 17:24                     ` Davidlohr Bueso
2017-11-09 17:30                       ` Peter Zijlstra
2017-11-29 15:29   ` [PATCH v8 1/6] lib/dlock-list: Distributed and lock-protected lists Davidlohr Bueso
2017-10-31 18:50 ` [PATCH v8 2/6] vfs: Remove unnecessary list_for_each_entry_safe() variants Waiman Long
2017-10-31 18:50 ` [PATCH v8 3/6] vfs: Use dlock list for superblock's inode list Waiman Long
2017-10-31 18:50 ` [PATCH v8 4/6] lib/dlock-list: Make sibling CPUs share the same linked list Waiman Long
2017-11-01  8:38   ` Jan Kara
2017-10-31 18:50 ` [PATCH v8 5/6] lib/dlock-list: Enable faster lookup with hashing Waiman Long
2017-11-01  8:40   ` Jan Kara
2017-11-01 13:16     ` Waiman Long
2017-10-31 18:51 ` [PATCH v8 6/6] lib/dlock-list: Add an IRQ-safe mode to be used in interrupt handler Waiman Long
2017-10-31 21:29   ` Davidlohr Bueso
2017-11-29 15:26 ` Davidlohr Bueso [this message]
2017-11-29 15:31   ` [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list Waiman Long
2018-02-26  2:47 ` Dave Chinner
2018-02-26  4:05   ` 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=20171129152602.p4dzxhoaruza47ol@linux-n805 \
    --to=dave@stgolabs.net \
    --cc=andi@firstfloor.org \
    --cc=bfields@fieldses.org \
    --cc=boqun.feng@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=dchinner@redhat.com \
    --cc=jack@suse.com \
    --cc=jlayton@poochiereds.net \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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