From: Andrew Morton <akpm@linux-foundation.org>
To: Waiman Long <longman@redhat.com>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
Kees Cook <keescook@chromium.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
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>,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH 0/2] fs/dcache: Track # of negative dentries
Date: Tue, 28 Aug 2018 15:50:06 -0700 [thread overview]
Message-ID: <20180828155006.a6a94a7ba64ac4ce6b8b190c@linux-foundation.org> (raw)
In-Reply-To: <1535476780-5773-1-git-send-email-longman@redhat.com>
On Tue, 28 Aug 2018 13:19:38 -0400 Waiman Long <longman@redhat.com> wrote:
> This patchset is a reduced scope version of the
> patchset "fs/dcache: Track & limit # of negative dentries"
> (https://lkml.org/lkml/2018/7/12/586). Only the first 2 patches are
> included to track the number of negative dentries in the system as well
> as making negative dentries more easily reclaimed than positive ones.
>
> There are controversies on limiting number of negative dentries as it may
> make negative dentries special in term of how memory resources are to
> be managed in the kernel. However, I don't believe I heard any concern
> about tracking the number of negative dentries in the system. So it is
> better to separate that out and get it done with. We can deal with the
> controversial part later on.
Seems reasonable.
It would be nice to see testing results please. Quite comprehensive
ones.
And again, an apparently permanent feature of this patchset is that the
changelogs fail to provide descriptions of real-world problems with the
existing code. Please do provide those (comprehensive) descriptions and
demonstrate that these changes resolve those problems.
Also, a grumpynit: with 100% uniformity, the vfs presently refers to
negative dentries with the string "negative" in the identifier. This
patchset abbreviates that to "neg".
next prev parent reply other threads:[~2018-08-28 22:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 17:19 [PATCH 0/2] fs/dcache: Track # of negative dentries Waiman Long
2018-08-28 17:19 ` [PATCH 1/2] fs/dcache: Track & report number " Waiman Long
2018-08-29 0:11 ` Dave Chinner
2018-08-29 17:11 ` Waiman Long
2018-08-30 1:43 ` Dave Chinner
2018-08-30 21:49 ` Waiman Long
2018-08-31 14:31 ` Matthew Wilcox
2018-08-31 15:03 ` Waiman Long
2018-08-28 17:19 ` [PATCH 2/2] fs/dcache: Make negative dentries easier to be reclaimed Waiman Long
2018-08-28 22:13 ` Matthew Wilcox
2018-08-28 22:29 ` Waiman Long
2018-08-28 23:10 ` Linus Torvalds
2018-08-28 23:22 ` Andrew Morton
2018-08-29 1:18 ` Waiman Long
2018-08-29 1:18 ` Waiman Long
2018-08-28 23:01 ` Andrew Morton
2018-08-29 17:54 ` Paul E. McKenney
2018-08-29 20:03 ` Waiman Long
2018-08-29 21:04 ` Matthew Wilcox
2018-08-29 1:02 ` Dave Chinner
2018-08-29 19:34 ` Waiman Long
2018-08-30 1:12 ` Dave Chinner
2018-08-30 21:51 ` Waiman Long
2018-08-29 7:51 ` Michal Hocko
2018-08-29 19:58 ` Waiman Long
2018-08-30 7:20 ` Michal Hocko
2018-08-30 21:48 ` Waiman Long
2018-08-28 22:50 ` Andrew Morton [this message]
2018-08-28 22:54 ` [PATCH 0/2] fs/dcache: Track # of negative dentries 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=20180828155006.a6a94a7ba64ac4ce6b8b190c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=James.Bottomley@HansenPartnership.com \
--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=longman@redhat.com \
--cc=lwoodman@redhat.com \
--cc=mcgrof@kernel.org \
--cc=mhocko@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).