On Fri, Jul 06, 2018 at 03:32:52PM -0400, Waiman Long wrote: > The tracking and limit of negative dentries in a filesystem is a useful > addition. However, for users who want to reduce the kernel size as much > as possible, this feature will probably be on the chopping block. To > suit those users, a default-y config option DCACHE_LIMIT_NEG_ENTRY is > added so that the negative dentry tracking and limiting code can be > configured out, if necessary. > > Signed-off-by: Waiman Long <longman@xxxxxxxxxx> > --- > fs/Kconfig | 10 ++++++++++ > fs/dcache.c | 33 ++++++++++++++++++++++++++++++++- > include/linux/dcache.h | 2 ++ > kernel/sysctl.c | 2 ++ > 4 files changed, 46 insertions(+), 1 deletion(-) > > diff --git a/fs/Kconfig b/fs/Kconfig > index ac474a6..b521941 100644 > --- a/fs/Kconfig > +++ b/fs/Kconfig > @@ -113,6 +113,16 @@ source "fs/autofs/Kconfig" > source "fs/fuse/Kconfig" > source "fs/overlayfs/Kconfig" > > +# > +# Track and limit the number of negative dentries allowed in the system. > +# > +config DCACHE_LIMIT_NEG_ENTRY > + bool "Track & limit negative dcache entries" > + default y > + help > + This option enables the tracking and limiting of the total > + number of negative dcache entries allowable in the filesystem. > + If there's going to be a config option for this, it should be documented properly. I.e., why would someone want to turn this on, or turn it off? What are the tradeoffs? If unsure, should the user say y or n? I think there are way too many config options that were meaningful to the person writing the code but aren't meaningful to people configuring the kernel. - Eric
