From: Waiman Long <longman@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"Wangkai (Kevin,C)" <wangkai86@huawei.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"walters@verbum.org" <walters@verbum.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"Renjinyong (Renjinyong,
Business Support Dept)" <renjinyong@huawei.com>
Subject: Re: [PATCH] fs/dcache: dentries should free after files unlinked or directories removed
Date: Mon, 4 Sep 2017 17:45:48 -0400 [thread overview]
Message-ID: <dba65a0a-0f8c-a86c-0673-4f08d72770ff@redhat.com> (raw)
In-Reply-To: <20170904125930.GD1761@quack2.suse.cz>
On 09/04/2017 08:59 AM, Jan Kara wrote:
>
> So I agree they are somewhat different but not fundamentally different -
> e.g. total number of files in the file system can be easily so high that
> dentries + inodes cannot fit into RAM and thus you are in a very similar
> situation as with negative dentries. That's actually one of the reasons why
> people were trying to bend memcgs to account slab cache as well. But it
> didn't end anywhere AFAIK.
>
> The reason why I'm objecting is that the limit on the number of negative
> dentries is another tuning knob, it is for very specific cases, and most of
> sysadmins will have no clue how to set it properly (even I wouldn't have a
> good idea).
Thanks for letting me know which part of the patch you are objecting to.
As suggested by Linus, I can easily change the patch to do some kind of
auto-tuning depending on the positive-negative dentries ratio without
needing a user configurable kernel command line option. I added that
option to make the patch more flexible, but I do agree that most people
will likely leave it at the default value without ever using it.
>> Current dentry lookup is through a hash table. The lookup performance
>> will depend on the number of hashed slots as well as the number of
>> entries queued in each slot. So in general, lookup performance
>> deteriorates the more entries you put into a given slot. That is true no
>> matter how many slots you have allocated.
> Agreed, but with rhashtables the number of slots grows dynamically with the
> number of entries...
Currently, alloc_large_system_hash() is scaling the number of hash slots
according to the system memory size. That is adequate in most cases.
Using rhashtable will add a little bit of overhead into the hash index
computation, so we will probably see a little bit of slowdown with small
number of dentries and a bit of speed-up with large number of dentries.
That may not be a trade-off we would like to take.
Cheers,
Longman
next prev parent reply other threads:[~2017-09-04 21:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 9:54 [PATCH] fs/dcache: dentries should free after files unlinked or directories removed Wangkai
2017-08-25 7:06 ` Wangkai (Kevin,C)
2017-08-25 14:47 ` Jan Kara
2017-08-25 15:10 ` Colin Walters
2017-08-25 16:43 ` Linus Torvalds
2017-08-26 6:56 ` Wangkai (Kevin,C)
2017-08-26 16:18 ` Linus Torvalds
2017-08-27 15:05 ` Waiman Long
2017-08-31 7:53 ` Jan Kara
2017-08-31 16:27 ` Waiman Long
2017-09-04 12:59 ` Jan Kara
2017-09-04 15:48 ` Linus Torvalds
2017-09-04 21:45 ` Waiman Long [this message]
2017-08-28 6:31 ` Wangkai (Kevin,C)
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=dba65a0a-0f8c-a86c-0673-4f08d72770ff@redhat.com \
--to=longman@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=renjinyong@huawei.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=walters@verbum.org \
--cc=wangkai86@huawei.com \
/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).