On Wed, Feb 25, 2009 at 12:01:10AM -0800, Matthew Ingersoll wrote: ... > Looking at the vblade code, it uses the system calls open, read and > write. So I think the main question would be, what makes it so the > writes don't overlap? Didn't see any locking, is it another subsystem > that handles the organization?
No, just the kernel. The process scheduler can schedule both vblade processes, and so I would not expect order of write operations to be preserved reliably. Although it's true that there's only one page cache, the buffers of each vblade process are independent. In short, using two vblade processes on the same backing store in this way makes me very uncomfortable. It hasn't been tested, but even with testing, race conditions are not always going to be noticed. It seems like using a single process capable of using more than one local interface would be a more straightforward approach. -- Ed Cashin <ecas...@coraid.com> ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Aoetools-discuss mailing list Aoetools-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aoetools-discuss
