From: Dave Hansen <dave.hansen@intel.com>
To: Li Wang <liwang@ubuntukylin.com>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
Zefan Li <lizefan@huawei.com>, Matthew Wilcox <matthew@wil.cx>
Subject: Re: [PATCH 0/3] Fadvise: Directory level page cache cleaning support
Date: Mon, 30 Dec 2013 11:18:15 -0800 [thread overview]
Message-ID: <52C1C6F7.8010809@intel.com> (raw)
In-Reply-To: <cover.1388409686.git.liwang@ubuntukylin.com>
On 12/30/2013 05:45 AM, Li Wang wrote:
> This patch extends 'fadvise' to support directory level page cache
> cleaning. The call to posix_fadvise(fd, 0, 0, POSIX_FADV_DONTNEED)
> with 'fd' referring to a directory will recursively reclaim page cache
> entries of files inside 'fd'. For secruity concern, those inodes
> which the caller does not own appropriate permissions will not
> be manipulated.
Why is this necessary to do in the kernel? Why not leave it to
userspace to walk the filesystem(s)?
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@intel.com>
To: Li Wang <liwang@ubuntukylin.com>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Cong Wang <xiyou.wangcong@gmail.com>,
Zefan Li <lizefan@huawei.com>, Matthew Wilcox <matthew@wil.cx>
Subject: Re: [PATCH 0/3] Fadvise: Directory level page cache cleaning support
Date: Mon, 30 Dec 2013 11:18:15 -0800 [thread overview]
Message-ID: <52C1C6F7.8010809@intel.com> (raw)
In-Reply-To: <cover.1388409686.git.liwang@ubuntukylin.com>
On 12/30/2013 05:45 AM, Li Wang wrote:
> This patch extends 'fadvise' to support directory level page cache
> cleaning. The call to posix_fadvise(fd, 0, 0, POSIX_FADV_DONTNEED)
> with 'fd' referring to a directory will recursively reclaim page cache
> entries of files inside 'fd'. For secruity concern, those inodes
> which the caller does not own appropriate permissions will not
> be manipulated.
Why is this necessary to do in the kernel? Why not leave it to
userspace to walk the filesystem(s)?
next prev parent reply other threads:[~2013-12-30 19:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-30 13:45 [PATCH 0/3] Fadvise: Directory level page cache cleaning support Li Wang
2013-12-30 13:45 ` Li Wang
2013-12-30 13:45 ` [PATCH 1/3] VFS: Add the declaration of shrink_pagecache_parent Li Wang
2013-12-30 13:45 ` Li Wang
2013-12-30 13:45 ` [PATCH 2/3] Add shrink_pagecache_parent Li Wang
2013-12-30 13:45 ` Li Wang
2014-01-02 23:55 ` Andrew Morton
2014-01-02 23:55 ` Andrew Morton
2014-01-06 13:30 ` Dave Chinner
2014-01-06 13:30 ` Dave Chinner
2014-01-08 2:06 ` Li Wang
2014-01-08 2:06 ` Li Wang
2014-01-15 0:22 ` Dave Chinner
2014-01-15 0:22 ` Dave Chinner
2013-12-30 13:45 ` [PATCH 3/3] Fadvise: Add the ability for directory level page cache cleaning Li Wang
2013-12-30 13:45 ` Li Wang
2013-12-30 14:57 ` [PATCH 0/3] Fadvise: Directory level page cache cleaning support Matthew Wilcox
2013-12-30 14:57 ` Matthew Wilcox
2013-12-30 19:18 ` Dave Hansen [this message]
2013-12-30 19:18 ` Dave Hansen
2013-12-30 19:40 ` Andreas Dilger
2013-12-30 19:40 ` Andreas Dilger
2013-12-30 21:33 ` Dave Hansen
2013-12-30 21:33 ` Dave Hansen
2014-01-02 12:44 ` Li Wang
2014-01-02 12:44 ` Li Wang
2014-01-02 18:35 ` Dave Hansen
2014-01-02 18:35 ` Dave Hansen
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=52C1C6F7.8010809@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwang@ubuntukylin.com \
--cc=lizefan@huawei.com \
--cc=matthew@wil.cx \
--cc=viro@zeniv.linux.org.uk \
--cc=xiyou.wangcong@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.