On Thu, Apr 16, 2015 at 08:36:20AM +1000, Dave Chinner wrote: > Bikeshedding: I think this would be better suited to inode_dio_begin() > and inode_dio_end() because now we are trying to say "this is where > the DIO starts, and this is where it ends". It's not really > "reference counting" interface, we're trying to annotate the > boundaries of where DIO iis protected against truncate.... *nod* And while we are at, inode_dio_begin() could be static inline just fine. > And, realistically, if we are pushing this up into the filesystems > again, we should push it up into *all* filesystems and get rid of it > completely from the DIO layer. That way no new twisty passages in > the direct IO code are needed. Maybe... FWIW, since the code *checking* ->i_dio_count is already inside the individual filesystems (and right now I'm trying to verify it), we might as well have the code changing it there as well. AFAICS, the main problem with that is the need to do it after the end of async operation. Sure, we do have callbacks, but we'd need something like * start protection * submit DIO * if that has failed synchronously, drop protection and fuck off * otherwise let the callback deal with dropping it. What's more, we'd get not just a slew of boilerplate callbacks, but make life interesting for branch predictor - indirect calls are not fun... -- 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
