From: Li Wang <liwang-qfb7ZC4agRC9jIzG8Sm66w@public.gmane.org>
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>,
linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Milosz Tanski <milosz-B5zB6C1i6pkAvxtiuMwx3w@public.gmane.org>,
Li Wang <liwang-qfb7ZC4agRC9jIzG8Sm66w@public.gmane.org>
Subject: [PATCH 0/7] Cifs and Ceph: Uncache single no-data page in readpage()
Date: Mon, 11 Nov 2013 23:27:22 +0800 [thread overview]
Message-ID: <cover.1384183054.git.liwang@ubuntukylin.com> (raw)
Currently, the page allocated into fscache in readpage()
for Cifs and Ceph does not be uncached if no data read due
to io error. This patch fixes this. fscache_readpages_cancel()
is for this kind of job but taking list read * as input, so
a new routine take page * as input is introduced.
Li Wang (7):
Fscache: Introduce new API fscache_readpage_cancel()
Fscache: Implement uncaching single no-data page
Ceph: Introduce routine for uncaching single no-data page
Ceph: Uncaching no-data page in readpage()
Cifs: Introduce routine for uncaching single no-data page
Cifs: Implement uncaching single no-data page
Cifs: Uncaching no-data page in readpage()
fs/ceph/addr.c | 1 +
fs/ceph/cache.h | 13 +++++++++++++
fs/cifs/file.c | 4 +++-
fs/cifs/fscache.c | 7 +++++++
fs/cifs/fscache.h | 13 +++++++++++++
fs/fscache/page.c | 8 ++++++++
include/linux/fscache.h | 11 +++++++++++
7 files changed, 56 insertions(+), 1 deletion(-)
--
1.7.9.5
WARNING: multiple messages have this Message-ID (diff)
From: Li Wang <liwang@ubuntukylin.com>
To: linux-kernel@vger.kernel.org
Cc: ceph-devel@vger.kernel.org, Sage Weil <sage@inktank.com>,
linux-fsdevel@vger.kernel.org, linux-cifs@vger.kernel.org,
Milosz Tanski <milosz@adfin.com>,
Li Wang <liwang@ubuntukylin.com>
Subject: [PATCH 0/7] Cifs and Ceph: Uncache single no-data page in readpage()
Date: Mon, 11 Nov 2013 23:27:22 +0800 [thread overview]
Message-ID: <cover.1384183054.git.liwang@ubuntukylin.com> (raw)
Currently, the page allocated into fscache in readpage()
for Cifs and Ceph does not be uncached if no data read due
to io error. This patch fixes this. fscache_readpages_cancel()
is for this kind of job but taking list read * as input, so
a new routine take page * as input is introduced.
Li Wang (7):
Fscache: Introduce new API fscache_readpage_cancel()
Fscache: Implement uncaching single no-data page
Ceph: Introduce routine for uncaching single no-data page
Ceph: Uncaching no-data page in readpage()
Cifs: Introduce routine for uncaching single no-data page
Cifs: Implement uncaching single no-data page
Cifs: Uncaching no-data page in readpage()
fs/ceph/addr.c | 1 +
fs/ceph/cache.h | 13 +++++++++++++
fs/cifs/file.c | 4 +++-
fs/cifs/fscache.c | 7 +++++++
fs/cifs/fscache.h | 13 +++++++++++++
fs/fscache/page.c | 8 ++++++++
include/linux/fscache.h | 11 +++++++++++
7 files changed, 56 insertions(+), 1 deletion(-)
--
1.7.9.5
next reply other threads:[~2013-11-11 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 15:27 Li Wang [this message]
2013-11-11 15:27 ` [PATCH 0/7] Cifs and Ceph: Uncache single no-data page in readpage() Li Wang
2013-11-11 15:27 ` [PATCH 1/7] Fscache: Introduce new API fscache_readpage_cancel() Li Wang
2013-11-11 15:27 ` [PATCH 2/7] Fscache: Implement uncaching single no-data page Li Wang
2013-11-11 15:27 ` [PATCH 4/7] Ceph: Uncaching no-data page in readpage() Li Wang
2013-11-11 15:27 ` [PATCH 5/7] Cifs: Introduce routine for uncaching single no-data page Li Wang
2013-11-11 15:27 ` [PATCH 6/7] Cifs: Implement " Li Wang
2013-11-11 15:27 ` [PATCH 7/7] Cifs: Uncaching no-data page in readpage() Li Wang
[not found] ` <cover.1384183054.git.liwang-qfb7ZC4agRC9jIzG8Sm66w@public.gmane.org>
2013-11-11 15:27 ` [PATCH 3/7] Ceph: Introduce routine for uncaching single no-data page Li Wang
2013-11-11 15:27 ` Li Wang
2013-11-11 16:19 ` [PATCH 0/7] Cifs and Ceph: Uncache single no-data page in readpage() Milosz Tanski
2013-11-11 16:19 ` Milosz Tanski
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=cover.1384183054.git.liwang@ubuntukylin.com \
--to=liwang-qfb7zc4agrc9jizg8sm66w@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=milosz-B5zB6C1i6pkAvxtiuMwx3w@public.gmane.org \
--cc=sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org \
/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.