linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Lovenberg <scott.lovenberg@gmail.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: Steve French <smfrench@gmail.com>,
	linux-fsdevel@vger.kernel.org, linux-cifs-client@lists.samba.org
Subject: Re: [linux-cifs-client] [PATCH] cifs: implement drop_inode superblock op
Date: Wed, 26 May 2010 19:19:11 -0400	[thread overview]
Message-ID: <4BFDAC6F.2090604@gmail.com> (raw)
In-Reply-To: <20100525200920.774cf77e@corrin.poochiereds.net>


>> Any rough idea of performance or memory savings (even in something
>> artificial like dbench run)?
>>
>>      
> It's more of a memory savings thing. When I mount with -o noserverino
> and run fsstress on the mount, I'd regularly see the size of the
> cifs_inode_cache hit 60M or more (on a client with 1G RAM). With this
> patch in place, it rarely goes over 2M in size.
>
> Eventually, memory pressure will force the size to go down, but if we
> know that they'll never be used again (which is the case with
> noserverino), it's better to go ahead and just free them.
>
>    
I take it this overrides the behavior of the vfs_cache_pressure before 
the memory pressure makes reclaiming cache necessary?

  reply	other threads:[~2010-05-26 23:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25 19:24 [PATCH] cifs: implement drop_inode superblock op Jeff Layton
2010-05-25 22:14 ` Steve French
2010-05-26  0:09   ` Jeff Layton
2010-05-26 23:19     ` Scott Lovenberg [this message]
2010-05-27 13:38       ` [linux-cifs-client] " Jeff Layton
2010-05-27 14:51         ` Steve French
2010-05-27 15:20           ` Jeff Layton
2010-05-26  2:16 ` Raja R Harinath

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=4BFDAC6F.2090604@gmail.com \
    --to=scott.lovenberg@gmail.com \
    --cc=jlayton@redhat.com \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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 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).