From: "Yan, Zheng" <zheng.z.yan@intel.com>
To: sage@inktank.com
Cc: ceph-devel@vger.kernel.org, alex.elder@linaro.org
Subject: Re: [PATCH 1/3] libceph: call r_unsafe_callback when unsafe reply is received
Date: Mon, 01 Jul 2013 15:28:39 +0800 [thread overview]
Message-ID: <51D12FA7.1090605@intel.com> (raw)
In-Reply-To: <1372056089-11603-1-git-send-email-zheng.z.yan@intel.com>
ping
I think this patch should goes into 3.11 or fix the issue by other means
On 06/24/2013 02:41 PM, Yan, Zheng wrote:
> From: "Yan, Zheng" <zheng.z.yan@intel.com>
>
> We can't use !req->r_sent to check if OSD request is sent for the
> first time, this is because __cancel_request() zeros req->r_sent
> when OSD map changes. Rather than adding a new variable to struct
> ceph_osd_request to indicate if it's sent for the first time, We
> can call the unsafe callback only when unsafe OSD reply is received.
> If OSD's first reply is safe, just skip calling the unsafe callback.
>
> The purpose of unsafe callback is adding unsafe request to a list,
> so that fsync(2) can wait for the safe reply. fsync(2) doesn't need
> to wait for a write(2) that hasn't returned yet. So it's OK to add
> request to the unsafe list when the first OSD reply is received.
> (ceph_sync_write() returns after receiving the first OSD reply)
>
> Signed-off-by: Yan, Zheng <zheng.z.yan@intel.com>
> ---
> net/ceph/osd_client.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/net/ceph/osd_client.c b/net/ceph/osd_client.c
> index 540dd29..dd47889 100644
> --- a/net/ceph/osd_client.c
> +++ b/net/ceph/osd_client.c
> @@ -1337,10 +1337,6 @@ static void __send_request(struct ceph_osd_client *osdc,
>
> ceph_msg_get(req->r_request); /* send consumes a ref */
>
> - /* Mark the request unsafe if this is the first timet's being sent. */
> -
> - if (!req->r_sent && req->r_unsafe_callback)
> - req->r_unsafe_callback(req, true);
> req->r_sent = req->r_osd->o_incarnation;
>
> ceph_con_send(&req->r_osd->o_con, req->r_request);
> @@ -1431,8 +1427,6 @@ static void handle_osds_timeout(struct work_struct *work)
>
> static void complete_request(struct ceph_osd_request *req)
> {
> - if (req->r_unsafe_callback)
> - req->r_unsafe_callback(req, false);
> complete_all(&req->r_safe_completion); /* fsync waiter */
> }
>
> @@ -1559,14 +1553,20 @@ static void handle_reply(struct ceph_osd_client *osdc, struct ceph_msg *msg,
> mutex_unlock(&osdc->request_mutex);
>
> if (!already_completed) {
> + if (req->r_unsafe_callback &&
> + result >= 0 && !(flags & CEPH_OSD_FLAG_ONDISK))
> + req->r_unsafe_callback(req, true);
> if (req->r_callback)
> req->r_callback(req, msg);
> else
> complete_all(&req->r_completion);
> }
>
> - if (flags & CEPH_OSD_FLAG_ONDISK)
> + if (flags & CEPH_OSD_FLAG_ONDISK) {
> + if (req->r_unsafe_callback && already_completed)
> + req->r_unsafe_callback(req, false);
> complete_request(req);
> + }
>
> done:
> dout("req=%p req->r_linger=%d\n", req, req->r_linger);
>
next prev parent reply other threads:[~2013-07-01 7:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 6:41 [PATCH 1/3] libceph: call r_unsafe_callback when unsafe reply is received Yan, Zheng
2013-06-24 6:41 ` [PATCH 2/3] mds: fix cap revoke race Yan, Zheng
2013-06-24 8:00 ` Yan, Zheng
2013-06-24 8:19 ` Yan, Zheng
2013-06-24 6:41 ` [PATCH 3/3] mds: fix race between cap issue and revoke Yan, Zheng
2013-06-24 8:16 ` Yan, Zheng
2013-07-01 7:28 ` Yan, Zheng [this message]
2013-07-01 19:46 ` [PATCH 1/3] libceph: call r_unsafe_callback when unsafe reply is received Sage Weil
2013-07-03 21:57 ` Sage Weil
2013-07-03 22:07 ` Milosz Tanski
2013-07-03 22:10 ` Sage Weil
2013-07-03 22:43 ` Yan, Zheng
2013-07-08 14:42 ` Milosz Tanski
2013-07-08 19:58 ` Milosz Tanski
2013-07-08 20:30 ` Yan, Zheng
2013-07-08 21:16 ` Milosz Tanski
2013-07-25 15:43 ` Milosz Tanski
2013-07-03 22:18 ` Alex Elder
2013-07-03 22:22 ` Yan, Zheng
2013-07-03 22:26 ` Sage Weil
2013-07-03 22:32 ` Sage Weil
2013-07-02 13:07 ` Alex Elder
2013-07-02 14:27 ` Yan, Zheng
2013-07-02 18:10 ` Sage Weil
2013-07-02 18:11 ` Alex Elder
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=51D12FA7.1090605@intel.com \
--to=zheng.z.yan@intel.com \
--cc=alex.elder@linaro.org \
--cc=ceph-devel@vger.kernel.org \
--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