So I do not think mclock_client queue works the way you’re hoping it does. For
categorization purposes it joins the operation class and the client identifier
with the intent that that will execute operations among clients more evenly
(i.e., it won’t favor one client over another).
However, it w
I am now trying to run tests to see how mclock_client queue works on mimic. But
when I tried to config tag (r,w,l) of each client, I found there are no options
to distinguish different clients.
All I got are following options for mclock_opclass, which are used to
distinguish different types of o
