This repository has been archived by the owner on Nov 17, 2022. It is now read-only.
How does Mpool manage two layers of devices? #2
Unanswered
sherlockwu
asked this question in
Q&A
Replies: 2 comments
-
Please see the Concepts section of the Wiki for a high-level overview. In short, mpool itself simply provides the ability to allocate an object in one of the configured media classes (capacity or staging). In the context of HSE (which is to say when HSE is the mpool client), it is HSE that decides in which media class to allocate an object based on what it stores. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I see, that makes sense. I will head to look into HSE then. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Mpool team,
Thanks for putting your project on GitHub!
Could you help to clarify something to help understand what Mpool target for?
Looks like Mpool is indeed the module that does heterogeneous devices management for the HSE key-value store project, is this correct?
How does Mpool manage two layers of devices? Is it caching on the faster layer? Could you provide some description on this? thanks
Kan
Beta Was this translation helpful? Give feedback.
All reactions