[Sheepdog] Sheepdog 0.3.0 schedule and 0.4.0 plan
zituan at taobao.com
Tue Nov 15 09:50:58 CET 2011
On Tue, Nov 15, 2011 at 3:40 PM, Christoph Hellwig <hch at infradead.org> wrote:
> On Tue, Nov 15, 2011 at 11:05:33AM +0900, MORITA Kazutaka wrote:
>> I finished all of the cluster driver implementation we planed, so I
>> think of releasing 0.3.0 this weekend. If you have pending patches
>> for 0.3.0, please send them until Nov 18th. I'll spend this week
>> testing Sheepdog.
>> The planned big features for 0.4.0 are as follows:
>> - add write-cache support
> That description sounds a bit odd. I've started hacking support on
> a traditional writeback cache - that is data still gets written out
> using normal write on all storage nodes, but we can skip the O_SYNC
> flag. Then the client sends a cache flush command and we do a syncfs
does this 'client' mean qemu block driver ?
my other question is , if we only bypass the O_SYNC flag, and without
at local disk(or memory), so lots of read traffic maybe transfered
then how can we increase the read side performance?
so I think we can't discard the cache prefetch or read ahead support.
> system call on all nodes to make sure data is on stable store from
> I've implemented the client side, and a local implementation of the
> cache flushing, but so far I've failed finding a way to forward it
> to each node that has an object for the given image exactly once.
> If you're interested I can send the current WIP patches for this out to
> the list.
we really appreciate it!
> sheepdog mailing list
> sheepdog at lists.wpkg.org
This email (including any attachments) is confidential and may be legally privileged. If you received this email in error, please delete it immediately and do not copy it or use it for any purpose or disclose its contents to any other person. Thank you.
More information about the sheepdog