All of lore.kernel.org
 help / color / mirror / Atom feed
From: ronnie sahlberg <ronniesahlberg@gmail.com>
To: Shyam Prasad N <nspmangalore@gmail.com>
Cc: Steve French <smfrench@gmail.com>,
	Ronnie Sahlberg <lsahlber@redhat.com>,
	linux-cifs <linux-cifs@vger.kernel.org>
Subject: Re: [PATCH] cifs: Add a laundromat thread for cached directories
Date: Fri, 7 Jul 2023 16:41:59 +1000	[thread overview]
Message-ID: <CAN05THTazZByLPSgrcMg8LuMhAT2=0r+znOnUkGuSdtWPVUtGw@mail.gmail.com> (raw)
In-Reply-To: <CANT5p=qxZjxpqx49BO7G-8=se2_5gEPyLOi_W-sUDm0p7VhbEQ@mail.gmail.com>

On Fri, 7 Jul 2023 at 16:37, Shyam Prasad N <nspmangalore@gmail.com> wrote:
>
> On Fri, Jul 7, 2023 at 11:20 AM ronnie sahlberg
> <ronniesahlberg@gmail.com> wrote:
> >
> > We can only cache a limited amount of entries.
> > We need to force entries to be dropped from the cache at regular
> > intervals to make room for potential new entries/different
> > directories.
> >
> > Access patterns change over time and what is the "hot" directory will
> > also change over time so we need to drop entries to make sure that
> > when some directory becomes hot there will be decent chance that it
> > will be able to become cached.
> >
> > If a directory becomes "cold" we no longer want it to take up entries
> > in our cache.
> >
>
> Makes sense.
>
> However, the value of MAX_CACHED_FIDS to 16 seems very restrictive.
> And as Steve suggested, 30s expiry seems very aggressive.
> I think we can increase both.

We can and should increase it at some stage but lets keep it small and
short for now until we feel confident it is all stable.
Once we are confident it is good we can increase these quite a bit.

  reply	other threads:[~2023-07-07  6:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-06  2:32 [PATCH] cifs: Add a laundromat thread for cached directories Ronnie Sahlberg
2023-07-06  3:07 ` Steve French
2023-07-07  5:31   ` Shyam Prasad N
2023-07-07  5:50     ` ronnie sahlberg
2023-07-07  6:37       ` Shyam Prasad N
2023-07-07  6:41         ` ronnie sahlberg [this message]
2023-07-07 16:17         ` Steve French

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='CAN05THTazZByLPSgrcMg8LuMhAT2=0r+znOnUkGuSdtWPVUtGw@mail.gmail.com' \
    --to=ronniesahlberg@gmail.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=lsahlber@redhat.com \
    --cc=nspmangalore@gmail.com \
    --cc=smfrench@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.