On 09/30/05 17:15, Andrew Patterson wrote: >>Sorry but I completely fail to see this argument., locks it, then hangs. >> >>How will it "fail for most storage managament apps"? > > > Let's see, one example: > > Process A opens an attribute and writes to it. Process B opens another > attribute and writes to it, affecting the result that process A will see > from its subsequent read. I suppose you could lock every attribute, but > that would be very error-prone, and not allow much concurrency. Why should synchronization between Process A and Process B reading storage attributes take place in the kernel? They can synchronize in user space. Luben - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
