From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Minchan Kim <minchan.kim@gmail.com>,
Chris Mason <chris.mason@oracle.com>,
viro@zeniv.linux.org.uk, adilger.kernel@dilger.ca, tytso@mit.edu,
mfasheh@suse.com, jlbec@evilplan.org, matthew@wil.cx,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
ocfs2-devel@oss.oracle.com, linux-mm@kvack.org,
hch@infradead.org, ngupta@vflare.org, jeremy@goop.org,
JBeulich@novell.com, Kurt Hackel <kurt.hackel@oracle.com>,
npiggin@kernel.dk, Dave Mccracken <dave.mccracken@oracle.com>,
riel@redhat.com, avi@redhat.com,
Konrad Wilk <konrad.wilk@oracle.com>,
mel@csn.ul.ie, yinghan@google.com, gthelen@google.com,
torvalds@linux-foundation.org
Subject: Re: [PATCH V8 4/8] mm/fs: add hooks to support cleancache
Date: Sat, 16 Apr 2011 00:37:36 +0900 [thread overview]
Message-ID: <871v135xvj.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <20110415081054.79a164d3.akpm@linux-foundation.org> (Andrew Morton's message of "Fri, 15 Apr 2011 08:10:54 -0700")
Andrew Morton <akpm@linux-foundation.org> writes:
>> > Before I suggested a thing about cleancache_flush_page,
>> > cleancache_flush_inode.
>> >
>> > what's the meaning of flush's semantic?
>> > I thought it means invalidation.
>> > AFAIC, how about change flush with invalidate?
>>
>> I'm not sure the words "flush" and "invalidate" are defined
>> precisely or used consistently everywhere in computer
>> science, but I think that "invalidate" is to destroy
>> a "pointer" to some data, but not necessarily destroy the
>> data itself. And "flush" means to actually remove
>> the data. So one would "invalidate a mapping" but one
>> would "flush a cache".
>>
>> Since cleancache_flush_page and cleancache_flush_inode
>> semantically remove data from cleancache, I think flush
>> is a better name than invalidate.
>>
>> Does that make sense?
>>
>
> nope ;)
>
> Kernel code freely uses "flush" to refer to both invalidation and to
> writeback, sometimes in confusing ways. In this case,
> cleancache_flush_inode and cleancache_flush_page rather sound like they
> might write those things to backing store.
I'd like to mention about *_{get,put}_page too. In linux get/put is not
meaning read/write. There is {get,put}_page those are refcount stuff
(Yeah, and I felt those methods does refcount by quick read. But it
seems to be false. There is no xen codes, so I don't know actually
though.).
And I agree, I also think the needing thing is consistency on the linux
codes (term).
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-04-15 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 21:17 Dan Magenheimer
2011-04-14 23:37 ` Minchan Kim
2011-04-15 14:47 ` Dan Magenheimer
2011-04-15 15:10 ` Andrew Morton
2011-04-15 15:32 ` Dan Magenheimer
2011-04-15 15:37 ` OGAWA Hirofumi [this message]
2011-04-15 18:53 ` Dan Magenheimer
2011-04-18 5:32 ` Minchan Kim
2011-04-26 16:00 ` Dan Magenheimer
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=871v135xvj.fsf@devron.myhome.or.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=JBeulich@novell.com \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=chris.mason@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=dave.mccracken@oracle.com \
--cc=gthelen@google.com \
--cc=hch@infradead.org \
--cc=jeremy@goop.org \
--cc=jlbec@evilplan.org \
--cc=konrad.wilk@oracle.com \
--cc=kurt.hackel@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew@wil.cx \
--cc=mel@csn.ul.ie \
--cc=mfasheh@suse.com \
--cc=minchan.kim@gmail.com \
--cc=ngupta@vflare.org \
--cc=npiggin@kernel.dk \
--cc=ocfs2-devel@oss.oracle.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=yinghan@google.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