Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2018-02-25 Thread Waiman Long
On 02/25/2018 09:47 PM, Dave Chinner wrote: > Hi Waiman, > > What's happened to this patchset? Any plans to repost a more recent > version? > > FYI, I just ran a workload that hit 60% CPU usage on sb inode list > lock contention - a multithreaded bulkstat scan of an XFS filesystem > with millions

Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2018-02-25 Thread Waiman Long
On 02/25/2018 09:47 PM, Dave Chinner wrote: > Hi Waiman, > > What's happened to this patchset? Any plans to repost a more recent > version? > > FYI, I just ran a workload that hit 60% CPU usage on sb inode list > lock contention - a multithreaded bulkstat scan of an XFS filesystem > with millions

Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2018-02-25 Thread Dave Chinner
Hi Waiman, What's happened to this patchset? Any plans to repost a more recent version? FYI, I just ran a workload that hit 60% CPU usage on sb inode list lock contention - a multithreaded bulkstat scan of an XFS filesystem with millions of inodes on SSDs. last time I ran this (about 18 months

Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2018-02-25 Thread Dave Chinner
Hi Waiman, What's happened to this patchset? Any plans to repost a more recent version? FYI, I just ran a workload that hit 60% CPU usage on sb inode list lock contention - a multithreaded bulkstat scan of an XFS filesystem with millions of inodes on SSDs. last time I ran this (about 18 months

Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2017-11-29 Thread Waiman Long
On 11/29/2017 10:26 AM, Davidlohr Bueso wrote: > 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

Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2017-11-29 Thread Waiman Long
On 11/29/2017 10:26 AM, Davidlohr Bueso wrote: > 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

Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2017-11-29 Thread Davidlohr Bueso
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

Re: [PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2017-11-29 Thread Davidlohr Bueso
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

[PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2017-10-31 Thread Waiman Long
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

[PATCH v8 0/6] vfs: Use dlock list for SB's s_inodes list

2017-10-31 Thread Waiman Long
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