From: Milosz Tanski <milosz@adfin.com>
To: Li Wang <liwang@ubuntukylin.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
Sage Weil <sage@inktank.com>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] ceph fscache: uncaching single no data page when error
Date: Fri, 20 Dec 2013 11:03:19 -0500 [thread overview]
Message-ID: <CANP1eJFyxBMg3x7Vbrdf2=CA2Oau6gLjpTduZgSadtMCje48iw@mail.gmail.com> (raw)
In-Reply-To: <cover.1387461299.git.liwang@ubuntukylin.com>
This looks legit to me.
- M
P.S: Sorry for the first HTML email, I blame gmail.
On Thu, Dec 19, 2013 at 9:03 AM, Li Wang <liwang@ubuntukylin.com> wrote:
> Currently, if one new page allocated into fscache in readpage(), however,
> with no data read into due to error encountered during reading from OSDs,
> the slot in fscache is not uncached. This patch fixes this.
>
> Li Wang (2):
> ceph: Introduce a routine for uncaching single no data page from
> fscache
> ceph: Uncaching no data page from fscache in readpage()
>
> fs/ceph/addr.c | 1 +
> fs/ceph/cache.h | 13 +++++++++++++
> 2 files changed, 14 insertions(+)
>
> --
> 1.7.9.5
>
--
Milosz Tanski
CTO
10 East 53rd Street, 37th floor
New York, NY 10022
p: 646-253-9055
e: milosz@adfin.com
prev parent reply other threads:[~2013-12-20 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 14:03 [PATCH 0/2] ceph fscache: uncaching single no data page when error Li Wang
2013-12-19 14:03 ` [PATCH 1/2] ceph fscache: Introduce a routine for uncaching single no data page from fscache Li Wang
2013-12-19 14:03 ` [PATCH 2/2] ceph fscache: Uncaching no data page from fscache in readpage() Li Wang
2013-12-20 16:03 ` Milosz Tanski [this message]
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='CANP1eJFyxBMg3x7Vbrdf2=CA2Oau6gLjpTduZgSadtMCje48iw@mail.gmail.com' \
--to=milosz@adfin.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwang@ubuntukylin.com \
--cc=sage@inktank.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;
as well as URLs for NNTP newsgroup(s).