Messages in this thread | | | Date | Fri, 30 Sep 2005 18:01:59 -0400 | From | Luben Tuikov <> | Subject | Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |