From: juncheng bai <baijuncheng@unitedstack.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: [RFD] how to save the status of object for the cloned image
Date: Wed, 17 Jun 2015 17:36:07 +0800 [thread overview]
Message-ID: <55813F87.7010106@unitedstack.com> (raw)
Hi.
For cloned image, it is stateless about the object. when the write
offset is smaller than the parent_ovelap,it need to call
rbd_img_obj_exists_submit to check the object status every time.
I want to save the status of the object which it is within the scope
of parent_overlap.
The rbd client io unit is object, so i design that use idr to save
the status. The id of object is equal to write_offset >> obj_order.
In the idr, said object already exists. And the idr can provide a
quick query.
In this way, don't need the server do anything, but need query again
when remap.
Looking forward to your opinion.
Cheers.
----
juncheng bai
next reply other threads:[~2015-06-17 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 9:36 juncheng bai [this message]
2015-06-17 10:25 ` [RFD] how to save the status of object for the cloned image Ilya Dryomov
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=55813F87.7010106@unitedstack.com \
--to=baijuncheng@unitedstack.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@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.