From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============5998425839312026667==" MIME-Version: 1.0 From: Al Viro To: lkp@lists.01.org Subject: Re: [dcache_{readdir, dir_lseek}() users] 4e82901cd6: reaim.jobs_per_min -49.1% regression Date: Sun, 26 Jun 2016 19:06:04 +0100 Message-ID: <20160626180604.GW14480@ZenIV.linux.org.uk> In-Reply-To: List-Id: --===============5998425839312026667== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Sun, Jun 26, 2016 at 10:13:32AM -0700, Linus Torvalds wrote: > On Sun, Jun 26, 2016 at 2:50 AM, Thorsten Leemhuis > wrote: > > > > Al, what's the status here? This made it on my 4.7 regressions report > > due to the "regression" keyword in the subject. > = > I don't think the tmpfs locking is going to get changed for 4.7. This > issue will likely only show up for some very specific microbenchmarks, > and the lockless next_positive one is likely too invasive for this > stage. So the problem is fixable, and not serious enough to worry > about for 4.7. FWIW, #work.dcache_readdir in vfs.git seems to recover the performance. Not sure if it's worth pushing right now, but if it ends up the next cycle stuff, I think it'll be worth Cc:stable. --===============5998425839312026667==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751853AbcFZSGN (ORCPT ); Sun, 26 Jun 2016 14:06:13 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:40534 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751485AbcFZSGM (ORCPT ); Sun, 26 Jun 2016 14:06:12 -0400 Date: Sun, 26 Jun 2016 19:06:04 +0100 From: Al Viro To: Linus Torvalds Cc: Thorsten Leemhuis , "Huang, Ying" , LKP , LKML Subject: Re: [LKP] [lkp] [dcache_{readdir, dir_lseek}() users] 4e82901cd6: reaim.jobs_per_min -49.1% regression Message-ID: <20160626180604.GW14480@ZenIV.linux.org.uk> References: <20160531081515.GC11635@yexl-desktop> <20160531134011.GB14480@ZenIV.linux.org.uk> <87bn3laffo.fsf@yhuang-dev.intel.com> <87h9dchzor.fsf@yhuang-dev.intel.com> <20160602162956.GH14480@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jun 26, 2016 at 10:13:32AM -0700, Linus Torvalds wrote: > On Sun, Jun 26, 2016 at 2:50 AM, Thorsten Leemhuis > wrote: > > > > Al, what's the status here? This made it on my 4.7 regressions report > > due to the "regression" keyword in the subject. > > I don't think the tmpfs locking is going to get changed for 4.7. This > issue will likely only show up for some very specific microbenchmarks, > and the lockless next_positive one is likely too invasive for this > stage. So the problem is fixable, and not serious enough to worry > about for 4.7. FWIW, #work.dcache_readdir in vfs.git seems to recover the performance. Not sure if it's worth pushing right now, but if it ends up the next cycle stuff, I think it'll be worth Cc:stable.