From: Eric Dumazet <eric.dumazet@gmail.com>
To: Glauber Costa <glommer@parallels.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
containers@lists.linux-foundation.org,
Pavel Emelyanov <xemul@parallels.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Hugh Dickins <hughd@google.com>, Nick Piggin <npiggin@kernel.dk>,
Andrea Arcangeli <aarcange@redhat.com>,
Rik van Riel <riel@redhat.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
James Bottomley <JBottomley@Parallels.com>,
David Chinner <david@fromorbit.com>
Subject: Re: [PATCH v3 2/4] Keep nr_dentry per super block
Date: Sun, 14 Aug 2011 19:38:42 +0200 [thread overview]
Message-ID: <1313343522.2798.11.camel@edumazet-laptop> (raw)
In-Reply-To: <1313334832-1150-3-git-send-email-glommer@parallels.com>
Le dimanche 14 août 2011 à 19:13 +0400, Glauber Costa a écrit :
> Now that we have per-sb shrinkers, it makes sense to have nr_dentries
> stored per sb as well. We turn them into per-cpu counters so we can
> keep acessing them without locking.
>
> Signed-off-by: Glauber Costa <glommer@parallels.com>
> }
> diff --git a/fs/super.c b/fs/super.c
> index 3f56a26..e95ac4f 100644
> --- a/fs/super.c
> +++ b/fs/super.c
> @@ -119,6 +119,9 @@ static struct super_block *alloc_super(struct file_system_type *type)
> s = NULL;
> goto out;
> }
> +
> + percpu_counter_init(&s->s_nr_dentry, 0);
> +
You should take care of possible error return at this point.
(We probably should check the percpu_counter_init() done in tcp_init(),
but they are done at boot time, with nearly no chance of failure)
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-14 17:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 15:13 [PATCH v3 0/4] Per-container dcache limitation Glauber Costa
[not found] ` <1313334832-1150-1-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2011-08-14 15:13 ` [PATCH v3 1/4] factor out single-shrinker code Glauber Costa
2011-08-15 6:43 ` Dave Chinner
2011-08-14 15:13 ` [PATCH v3 2/4] Keep nr_dentry per super block Glauber Costa
2011-08-14 17:38 ` Eric Dumazet [this message]
2011-08-14 15:13 ` [PATCH v3 3/4] limit nr_dentries per superblock Glauber Costa
2011-08-15 7:03 ` Dave Chinner
2011-08-15 7:12 ` Pekka Enberg
2011-08-15 10:46 ` Dave Chinner
2011-08-15 10:58 ` Pekka Enberg
2011-08-15 11:05 ` Pavel Emelyanov
2011-08-15 11:14 ` Pekka Enberg
2011-08-15 11:32 ` Pavel Emelyanov
2011-08-15 11:55 ` Pekka Enberg
2011-08-15 12:12 ` Pavel Emelyanov
2011-08-15 12:23 ` Pekka Enberg
2011-08-15 12:37 ` Pavel Emelyanov
2011-08-16 2:11 ` Dave Chinner
2011-08-14 15:13 ` [PATCH v3 4/4] parse options in the vfs level Glauber Costa
2011-08-14 15:39 ` Vasiliy Kulikov
2011-08-15 0:03 ` Glauber Costa
2011-08-15 7:09 ` Dave Chinner
2011-08-24 2:19 ` Glauber Costa
2011-08-17 5:43 ` [PATCH v3 0/4] Per-container dcache limitation Dave Chinner
2011-08-17 18:44 ` Glauber Costa
2011-08-18 1:27 ` Dave Chinner
2011-08-22 11:42 ` Glauber Costa
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=1313343522.2798.11.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=JBottomley@Parallels.com \
--cc=aarcange@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=david@fromorbit.com \
--cc=glommer@parallels.com \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=riel@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.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