From: Eric Dumazet <dada1@cosmosbay.com>
To: dipankar@in.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Fix file counting
Date: Thu, 16 Feb 2006 17:11:30 +0100 [thread overview]
Message-ID: <43F4A432.8070308@cosmosbay.com> (raw)
In-Reply-To: <20060216153301.GA1352@in.ibm.com>
Dipankar Sarma a écrit :
> Eric,
>
> Going by your patch, I converted my nr-files patch to use
> percpu counters - except that I just used the existing
> percpu counter code. This patch is untested, just for comments.
> If you agree with the approach, we can go with it. I will
> get some benchmark numbers measured on a 16-CPU box.
>
> Thanks
> Dipankar
>
>
>
> The way we do file struct accounting is not very suitable for batched
> freeing. For scalability reasons, file accounting was constructor/destructor
> based. This meant that nr_files was decremented only when
> the object was removed from the slab cache. This is
> susceptible to slab fragmentation. With RCU based file structure,
> consequent batched freeing and a test program like Serge's,
> we just speed this up and end up with a very fragmented slab -
>
> llm22:~ # cat /proc/sys/fs/file-nr
> 587730 0 758844
>
> At the same time, I see only a 2000+ objects in filp cache.
> The following patch I fixes this problem.
>
> This patch changes the file counting by removing the filp_count_lock.
> Instead we use a separate percpu counter, nr_files, for now and all
> accesses to it are through get_nr_files() api. In the sysctl
> handler for nr_files, we populate files_stat.nr_files before returning
> to user.
>
> Counting files as an when they are created and destroyed (as opposed
> to inside slab) allows us to correctly count open files with RCU.
>
> Signed-off-by: Dipankar Sarma <dipankar@in.ibm.com>
> ---
>
>
>
>
> fs/dcache.c | 2 -
> fs/file_table.c | 80 +++++++++++++++++++++++++++++++--------------------
> include/linux/file.h | 2 -
> include/linux/fs.h | 2 +
> kernel/sysctl.c | 5 ++-
> net/unix/af_unix.c | 2 -
> 6 files changed, 57 insertions(+), 36 deletions(-)
>
Hi Dipankar
I believe your patch is good.
However there is a bug in get_empty_filp() :
if security_file_alloc(f) returns TRUE : The goto fail_sec; is done and
fail_sec: does a file_free(f)
This means an extra percpu_counter_mod(&nr_files, -1L); will be done.
So I think you must apply this patch too :
fail_sec:
- file_free(f);
+ kmem_cache_free(filp_cachep, f);
fail:
return NULL;
(Ie no need for a delayed free done via rcu here, just a direct
kmem_cache_free() call)
Eric
next prev parent reply other threads:[~2006-02-16 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-16 15:33 Dipankar Sarma
2006-02-16 16:11 ` Eric Dumazet [this message]
2006-02-16 16:26 ` Dipankar Sarma
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=43F4A432.8070308@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=dipankar@in.ibm.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®