From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: viro@ZenIV.linux.org.uk, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, eric.dumazet@gmail.com,
paulmck@linux.vnet.ibm.com
Subject: Re: [PATCH 2/4] fs: Convert inode slab creation to use consistent parameters
Date: Mon, 25 Apr 2011 13:46:08 -0400 [thread overview]
Message-ID: <20110425174608.GA9779@infradead.org> (raw)
In-Reply-To: <1289201305-14866-3-git-send-email-david@fromorbit.com>
On Mon, Nov 08, 2010 at 06:28:23PM +1100, Dave Chinner wrote:
> From: Dave Chinner <dchinner@redhat.com>
>
> The inode slab creation functions in different filesystem don't all set up the
> slab caches correctly. Add a new flag SLAB_INODES that sets all the necessary
> flags for an inode slab cache and convert all the callers to use it. THis makes
> it easy to change the behaviour of all the inode slab caches in one go.
Any chance you could rediff this one ontop of current mainline and
resend it?
next prev parent reply other threads:[~2011-04-25 17:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 7:28 fs: inode rcu freeing and hash walking V2 Dave Chinner
2010-11-08 7:28 ` [PATCH 1/4] fs: pull inode->i_lock up out of writeback_single_inode Dave Chinner
2010-11-08 7:28 ` [PATCH 2/4] fs: Convert inode slab creation to use consistent parameters Dave Chinner
2011-04-25 17:46 ` Christoph Hellwig [this message]
2010-11-08 7:28 ` [PATCH 3/4] fs: Use RCU freeing of inodes via SLAB_DESTROY_BY_RCU Dave Chinner
2010-11-08 7:28 ` [PATCH 4/4] fs: rcu protect inode hash lookups Dave Chinner
2010-11-08 8:53 ` Eric Dumazet
2010-11-08 11:10 ` Christoph Hellwig
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=20110425174608.GA9779@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=viro@ZenIV.linux.org.uk \
/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).