From: majianpeng <majianpeng@gmail.com>
To: sage <sage@inktank.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: [PATCH 0/2] libceph: handle notarget requests.
Date: Tue, 16 Jul 2013 15:45:44 +0800 [thread overview]
Message-ID: <201307161545418344598@gmail.com> (raw)
In func ceph_osdc_start_request,there are two types:
A:nofail which mean if met error, the request will retry to do.
B:fail which mean if met error, the caller handle the error,like realse those relative pages.
But now, the code don't distinguish between them.
For caller which can met error, it must call __unregister_request if met error.It don't make any sense to retry to do because the caller
alreay handle failed routine like release papges.
For requests which in req_notarget,they only remap in func ceph_osdc_handle_map which update the epoch of osdmap.
But for reaseon which cause __map_request failed like ENOMEM,it won't update the epoch of osdmap,so notarget-requests won't remap for ever.
Jianpeng Ma (2):
libceph: For nofail == false, if __map_request failed,it should unregister.
libceph: Remap notarget requests in handle_timeout.
net/ceph/osd_client.c | 39 ++++++++++++++++++++++++++++++++++++++-
1 file changed, 38 insertions(+), 1 deletion(-)
reply other threads:[~2013-07-16 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201307161545418344598@gmail.com \
--to=majianpeng@gmail.com \
--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 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.