On Mon, Jul 22, 2013 at 11:25:17AM +1000, Dave Chinner wrote: > I'll just point out that it can make the whole thing worse, too. > For example, for ext3/4, the tmpfile being created has to be added > to the orphan inode list which is protected by a filesystem global > mutex. Hence scalability of O_TMPFILE is massively limited on > ext3/ext4 due to architectural issues within ext3/4. Other > filesystems will be more efficient, but because they have more > scalable/complex orphan inode handling it's going to take longer to > implement O_TMPFILE support for them....
Um... You do realize that the same architectural issues there will create exactly the same serialization when you are unlinking the sucker? I.e. with the "pick the name, create and open, unlink" sequence ext[34] will insert that inode into the same orphan list, creating the same contention... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
