We can go around and around on this and the end result will be that
I will have narrowed the locking problem down to the point that
only the processes which are actually using the resource have to
participate in the locking. In a traditional SMP OS, all processes
have to participate.
We can split up name spaces today with Al Viro's namespace
infrastructure.
But frankly for the cases where scalability matters, like a http
server, they are all going at the same files in a global file
space.
I still think ccClusters don't solve any new problems in the
locking space. "I get rid of it by putting people on different
filesystems" is not an answer which is unique to ccClusters, current
systems can do that.
-
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/