From: Waiman Long <longman@redhat.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Jonathan Corbet <corbet@lwn.net>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
Miklos Szeredi <mszeredi@redhat.com>,
Matthew Wilcox <willy@infradead.org>,
Larry Woodman <lwoodman@redhat.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
"Wangkai (Kevin C)" <wangkai86@huawei.com>
Subject: Re: [PATCH v6 0/7] fs/dcache: Track & limit # of negative dentries
Date: Fri, 6 Jul 2018 23:02:23 -0400 [thread overview]
Message-ID: <56b1d7ee-d362-f915-34fb-92173d512cbe@redhat.com> (raw)
In-Reply-To: <20180706222814.GE30522@ZenIV.linux.org.uk>
On 07/06/2018 06:28 PM, Al Viro wrote:
> On Fri, Jul 06, 2018 at 03:32:45PM -0400, Waiman Long wrote:
>
>> With a 4.18 based kernel, the positive & negative dentries lookup rates
>> (lookups per second) after initial boot on a 2-socket 24-core 48-thread
>> 64GB memory system with and without the patch were as follows: `
>>
>> Metric w/o patch neg_dentry_pc=0 neg_dentry_pc=1
>> ------ --------- --------------- ---------------
>> Positive dentry lookup 584299 586749 582670
>> Negative dentry lookup 1422204 1439994 1438440
>> Negative dentry creation 643535 652194 641841
>>
>> For the lookup rate, there isn't any signifcant difference with or
>> without the patch or with a zero or non-zero value of neg_dentry_pc.
> Sigh... What I *still* don't see (after all the iterations of the patchset)
> is any performance data on workloads that would be likely to feel the impact.
> Anything that seriously hits INCLUDE_PATH, for starters...
I wrote a simple microbenchmark that does a lot of open() system calls
to create positive or negative dentries. I was not seeing any noticeable
performance difference as long as not too many negative dentries were
created.
Please enlighten me on how kind of performance benchmark that you would
like me to run.
Thanks,
Longman
next prev parent reply other threads:[~2018-07-07 3:02 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 19:32 [PATCH v6 0/7] fs/dcache: Track & limit # of negative dentries Waiman Long
2018-07-06 19:32 ` [PATCH v6 1/7] fs/dcache: Track & report number " Waiman Long
2018-07-06 19:32 ` [PATCH v6 2/7] fs/dcache: Add sysctl parameter neg-dentry-pc as a soft limit on " Waiman Long
2018-07-06 19:32 ` [PATCH v6 3/7] fs/dcache: Enable automatic pruning of " Waiman Long
2018-07-06 19:32 ` [PATCH v6 4/7] fs/dcache: Spread negative dentry pruning across multiple CPUs Waiman Long
2018-07-06 19:32 ` [PATCH v6 5/7] fs/dcache: Add negative dentries to LRU head initially Waiman Long
2018-07-06 19:32 ` [PATCH v6 6/7] fs/dcache: Allow optional enforcement of negative dentry limit Waiman Long
2018-07-06 19:32 ` [PATCH v6 7/7] fs/dcache: Allow deconfiguration of negative dentry code to reduce kernel size Waiman Long
2018-07-06 21:54 ` Eric Biggers
2018-07-06 22:28 ` [PATCH v6 0/7] fs/dcache: Track & limit # of negative dentries Al Viro
2018-07-07 3:02 ` Waiman Long [this message]
2018-07-09 8:19 ` Michal Hocko
2018-07-09 16:01 ` Waiman Long
2018-07-10 14:27 ` Michal Hocko
2018-07-10 16:09 ` Waiman Long
2018-07-11 10:21 ` Michal Hocko
2018-07-11 15:13 ` Waiman Long
2018-07-11 17:42 ` James Bottomley
2018-07-11 19:07 ` Waiman Long
2018-07-11 19:21 ` James Bottomley
2018-07-12 15:54 ` Waiman Long
2018-07-12 16:04 ` James Bottomley
2018-07-12 16:26 ` Waiman Long
2018-07-12 17:33 ` James Bottomley
2018-07-13 15:32 ` Waiman Long
2018-07-12 16:49 ` Matthew Wilcox
2018-07-12 17:21 ` James Bottomley
2018-07-12 18:06 ` Linus Torvalds
2018-07-12 19:57 ` James Bottomley
2018-07-13 0:36 ` Dave Chinner
2018-07-13 15:46 ` James Bottomley
2018-07-13 23:17 ` Dave Chinner
2018-07-16 9:10 ` Michal Hocko
2018-07-16 14:42 ` James Bottomley
2018-07-16 9:09 ` Michal Hocko
2018-07-16 9:12 ` Michal Hocko
2018-07-16 12:41 ` Matthew Wilcox
2018-07-16 23:40 ` Andrew Morton
2018-07-17 1:30 ` Matthew Wilcox
2018-07-17 8:33 ` Michal Hocko
2018-07-19 0:33 ` Dave Chinner
2018-07-19 8:45 ` Michal Hocko
2018-07-19 9:13 ` Jan Kara
2018-07-18 18:39 ` Waiman Long
2018-07-18 16:17 ` Waiman Long
2018-07-19 8:48 ` Michal Hocko
2018-07-12 8:48 ` Michal Hocko
2018-07-12 16:12 ` Waiman Long
2018-07-12 23:16 ` Andrew Morton
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=56b1d7ee-d362-f915-34fb-92173d512cbe@redhat.com \
--to=longman@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jack@suse.cz \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=mszeredi@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
--cc=wangkai86@huawei.com \
--cc=willy@infradead.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).