At Wed, 09 May 2012 21:40:45 +0800, Liu Yuan wrote: > > If you are really concerned of this misbehavior, I think we try re-visit > Wuyue's patch. I guess we'll have to agree to disagree on what sheepdog write cache should be. I think it should work in the same way as a block device cache, but you think we should limit the usage to simplify the code and explain what's the limitation in the documentation. Wuyue's patch looks necessary from my point of view, but unnecessary to you. I don't intend to complain any more because it's you who implements the current object cache and it should work as you expect. If I need the write cache which works like a block device one, I should implement it as another cache feature. > > Anyway, I think now I am fine with adding a new option to disable object > cache globally, but I don't agree to disable it as default. If I can disable it, it's okay to me. I still think the feature which doesn't follow the block storage semantics shouldn't be default like asyncflush, though. |