On Tue, May 31, 2016 at 06:25:24PM +0200, Stef Bon wrote: > I've been thinking about the non serialized readdirs. I do not understand. > Readdirs have to be serialized, since the offset of the next readdir > (belonging to the opendir) is known when the current readdir is > finished: > "start where current left". They are serialized per struct file (and so'd lseek() on them, for that matter). So the state that is associated with an opened file is just fine; it's modifiable state associated with directory itself, and shared between all opened file that would be a problem. IOW, they can do readdir in parallel exactly in the cases when lseek done by one of them would not affect another. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
