On 12/6/16 10:49 PM, Amir Goldstein wrote: >> @@ -25,14 +28,35 @@ These code paths include not only the obvious read/write/mmap interfaces >> for manipulating files, but also cover all of the XFS extensions (such >> as space preallocation, additional inode flags, etc). >> .SH OPTIONS >> +.B xfs_io >> +commands may be run interactively (the default) or as arguments on the >> +command line. >> +Interactive mode always runs commands on the current open file, whilst commands >> +run from the command line may operate on all open files rather than the current >> +open file. > "operate on all open files" is ambiguous. does the loop go files -> cmds or > cmds -> files? this is part of the confusion IMO. How about adding something like: Files specified at the end of the command line are added to the file table first, then files specified in -c and -C commands are added. The last file in the file table is the current open file. -Eric -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
