Hi sage
I am refactoring the source code in order to support the extensible
tier (support redirect, dedup, external system)
I have a few question.
1. My understanding is that base pool contains all metadata for all
objects (do not evicted), and dedup pool or external systems contain
the object data.
Therefore, The big difference between the cache tier and the
extensible tier is whether base pool contains metadata (such as
object_info_t ) or not. Am i wrong?
2. Do you think the extensible tier should belong to cache_mode_t (in
maybe_handle_cache_detail()) ? or is it better to work independently
from cache tier.
3. Regarding promotion object and flushing work, I think start_copy() (in
promote_object()) and start_fush() can be reused in a simple
redirection case ("the object is in that other pool"), if we modify
the object (only metadata) is not evicted (removed). Is this right
way?
Thanks.
Myoungwon.
2017-04-13 0:51 GMT+09:00 Sage Weil <sweil@xxxxxxxxxx>:
> On Wed, 29 Mar 2017, myoungwon oh wrote:
>> Hi sage,
>>
>> I made two pads in order to discuss #3, #4.
>>
>> #3: http://pad.ceph.com/p/deduplication_how_do_we_chunk
>> #4: http://pad.ceph.com/p/deduplication_how_to_drive_dedup_process
>
> Updated!
> sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
