linux-nilfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Pekka Enberg <penberg@kernel.org>
Cc: Latchesar Ionkov <lucho@ionkov.net>,
	Dave Kleikamp <shaggy@kernel.org>,
	jfs-discussion@lists.sourceforge.net,
	Phillip Lougher <phillip@squashfs.org.uk>,
	Jan Kara <jack@suse.cz>, Kai Bankett <chaosman@ontika.net>,
	logfs@logfs.org, Frederic Weisbecker <fweisbec@gmail.com>,
	Anders Larsen <al@alarsen.net>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	William Irwin <wli@holomorphy.com>,
	"Dmitry V. Levin" <ldv@altlinux.org>,
	David Howells <dhowells@redhat.com>,
	Dustin Kirkland <dustin.kirkland@gazzang.com>,
	Andreas Dilger <adilger.kernel@dilger.ca>,
	Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz>,
	KONISHI Ryusuke <konishi.ryusuke@lab.ntt.co.jp>,
	Petr Vandrovec <petr@vandrovec.name>,
	linux-afs@lists.infradead.org,
	Alexey Khoroshilov <khoroshilov@ispras.ru>,
	linux-cifs@vger.kernel.org, Namjae Jeon <linkinjeon@gmail.com>,
	linux-nilfs@vger.kernel.org, fuse-devel@lists.source
Subject: Re: [RFC, PATCH] fs: push rcu_barrier() from deactivate_locked_super() to filesystems
Date: Fri, 8 Jun 2012 14:43:58 -0700	[thread overview]
Message-ID: <CA+55aFz_RpR+T3Yx-hMf3veW55xAu3GgtmefKs1ZUydp4hRu8w@mail.gmail.com> (raw)
In-Reply-To: <1339190930-17233-1-git-send-email-kirill.shutemov@linux.intel.com>

On Fri, Jun 8, 2012 at 2:28 PM, Kirill A. Shutemov
<kirill.shutemov@linux.intel.com> wrote:
> From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
>
> There's no reason to call rcu_barrier() on every deactivate_locked_super().
> We only need to make sure that all delayed rcu free inodes are flushed
> before we destroy related cache.
>
> Removing rcu_barrier() from deactivate_locked_super() affects some
> fas paths. E.g. on my machine exit_group() of a last process in IPC
> namespace takes 0.07538s. rcu_barrier() takes 0.05188s of that time.

I think we should just delete it.

kmem_cache_destroy() (at least for SLUB) already has:

                if (s->flags & SLAB_DESTROY_BY_RCU)
                        rcu_barrier();

in it. But I think it's too late - it gets called *after* we do
kmem_cache_close(), and I get the feeling that we should do it before.

Shouldn't that be sufficient? And if other slab allocators don't have
this, we should add it to them too.

Hmm?

              Linus

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2012-06-08 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 21:28 [RFC, PATCH] fs: push rcu_barrier() from deactivate_locked_super() to filesystems Kirill A. Shutemov
2012-06-08 21:43 ` Linus Torvalds [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-08 21:41 [RFC, PATCH, RESEND] " Kirill A. Shutemov
2012-06-08 22:00 ` [RFC, PATCH] " Kirill A. Shutemov
2012-06-08 22:06   ` Linus Torvalds
2012-06-08 22:25     ` Al Viro

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=CA+55aFz_RpR+T3Yx-hMf3veW55xAu3GgtmefKs1ZUydp4hRu8w@mail.gmail.com \
    --to=torvalds@linux-foundation.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=al@alarsen.net \
    --cc=chaosman@ontika.net \
    --cc=dhowells@redhat.com \
    --cc=dustin.kirkland@gazzang.com \
    --cc=fuse-devel@lists.source \
    --cc=fweisbec@gmail.com \
    --cc=jack@suse.cz \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=khoroshilov@ispras.ru \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=konishi.ryusuke@lab.ntt.co.jp \
    --cc=ldv@altlinux.org \
    --cc=linkinjeon@gmail.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=logfs@logfs.org \
    --cc=lucho@ionkov.net \
    --cc=mikulas@artax.karlin.mff.cuni.cz \
    --cc=penberg@kernel.org \
    --cc=petr@vandrovec.name \
    --cc=phillip@squashfs.org.uk \
    --cc=shaggy@kernel.org \
    --cc=wli@holomorphy.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).