From: Seth Jennings <sjenning@linux.vnet.ibm.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Jan Beulich <JBeulich@novell.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Hugh Dickins <hughd@google.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Nitin Gupta <ngupta@vflare.org>, Matthew Wilcox <matthew@wil.cx>,
Chris Mason <chris.mason@oracle.com>, Rik Riel <riel@redhat.com>
Subject: Re: [PATCH 1/4] mm: cleancache: s/flush/invalidate/
Date: Fri, 13 Jan 2012 15:12:48 -0600 [thread overview]
Message-ID: <4F109E50.5010104@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120113174306.GB16182@phenom.dumpdata.com>
On 01/13/2012 11:43 AM, Konrad Rzeszutek Wilk wrote:
> On Fri, Jan 13, 2012 at 09:16:33AM -0600, Seth Jennings wrote:
>> Hey Konrad,
>>
>> On 01/12/2012 02:36 PM, Konrad Rzeszutek Wilk wrote:
>>> From: Dan Magenheimer <dan.magenheimer@oracle.com>
>>>
>>> Per akpm suggestions alter the use of the term flush to be
>>> invalidate. The next patch will do this across all MM.
>>>
>>> This change is completely cosmetic.
>>>
>>> [v9: akpm@linux-foundation.org: change "flush" to "invalidate", part 3]
>>>
>>> Signed-off-by: Dan Magenheimer <dan.magenheimer@oracle.com>
>>> Reviewed-by: Konrad Wilk <konrad.wilk@oracle.com>
>>> Cc: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>>> Cc: Jan Beulich <JBeulich@novell.com>
>>> Cc: Seth Jennings <sjenning@linux.vnet.ibm.com>
>>> Cc: Jeremy Fitzhardinge <jeremy@goop.org>
>>> Cc: Hugh Dickins <hughd@google.com>
>>> Cc: Johannes Weiner <hannes@cmpxchg.org>
>>> Cc: Nitin Gupta <ngupta@vflare.org>
>>> Cc: Matthew Wilcox <matthew@wil.cx>
>>> Cc: Chris Mason <chris.mason@oracle.com>
>>> Cc: Rik Riel <riel@redhat.com>
>>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>> [v10: Fixed fs: move code out of buffer.c conflict change]
>>> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
>>> ---
>>> Documentation/vm/cleancache.txt | 37 +++++++++++++++++++------------------
>>> fs/block_dev.c | 2 +-
>>> fs/super.c | 2 +-
>>> include/linux/cleancache.h | 23 ++++++++++++++---------
>>> mm/cleancache.c | 19 ++++++++++---------
>>> mm/filemap.c | 2 +-
>>> mm/truncate.c | 10 +++++-----
>>> 7 files changed, 51 insertions(+), 44 deletions(-)
>> snip
>>> diff --git a/fs/block_dev.c b/fs/block_dev.c
>>> index 69a5b6f..d6d5f29 100644
>>> --- a/fs/block_dev.c
>>> +++ b/fs/block_dev.c
>>> @@ -110,7 +110,7 @@ void invalidate_bdev(struct block_device *bdev)
>>> /* 99% of the time, we don't need to flush the cleancache on the bdev.
>>> * But, for the strange corners, lets be cautious
>>> */
>>> - cleancache_flush_inode(mapping);
>>> + cleancache_invalidate_inode(mapping);
>>> }
>>> EXPORT_SYMBOL(invalidate_bdev);
>>
>> This hunk doesn't merge cleanly because there is no existing
>> cleancache code in fs/block_dev.c in v3.2 or any previous version.
>
> Hm, I am at 099469502f62fbe0d7e4f0b83a2f22538367f734 and I see
> that file with "cleancache_flush_inode" ?
>
> This is against v3.3-rc0, not 3.2.
Ah yes. Since no v3.3-rcX release has been tagged yet, I didn't
think to apply it there.
checkpatch clean, applies clean, builds clean
Consider all the patches in this set
Acked-by: Seth Jennings <sjenning@linux.vnet.ibm.com>
--
Seth
next prev parent reply other threads:[~2012-01-13 21:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 20:36 [PATCH] cleancache improvements for 3.4 (v1) Konrad Rzeszutek Wilk
2012-01-12 20:36 ` [PATCH 1/4] mm: cleancache: s/flush/invalidate/ Konrad Rzeszutek Wilk
2012-01-13 15:16 ` Seth Jennings
2012-01-13 17:43 ` Konrad Rzeszutek Wilk
2012-01-13 21:12 ` Seth Jennings [this message]
2012-01-12 20:36 ` [PATCH 2/4] mm: zcache/tmem/cleancache: s/flush/invalidate/ Konrad Rzeszutek Wilk
2012-01-12 20:36 ` [PATCH 3/4] mm: cleancache: report statistics via debugfs instead of sysfs Konrad Rzeszutek Wilk
2012-01-12 20:36 ` [PATCH 4/4] mm: cleancache: Use __read_mostly as appropiate Konrad Rzeszutek Wilk
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=4F109E50.5010104@linux.vnet.ibm.com \
--to=sjenning@linux.vnet.ibm.com \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jeremy@goop.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=ngupta@vflare.org \
--cc=riel@redhat.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