wrong latency info for flexfiles on layout return

["Mkrtchyan, Tigran" <tigran.mkrtchyan@xxxxxxx>]

Hi Trond et al.

by exploring data provided on layoutreturn I can see that some
information is wrong, in particular the IO latency completition
time for write:

{
   "iostats":[
      {
         "deviceAddr":"tcp://192.168.178.40.128.2",
         "duration":{
            "seconds":5,
            "nseconds":285924462
         },
         "readInfo":{
            "bytes":0,
            "latency":{
               "completitionTime":{
                  "seconds":0,
                  "nseconds":0
               },
               "bytesRequested":0,
               "opsCompleted":0,
               "busyTime":{
                  "seconds":0,
                  "nseconds":0
               },
               "opsRequested":0,
               "bytesCompleted":0,
               "bytesNotDelivered":0
            },
            "count":0
         },
         "fh":"01caffee00000000b1f9635e000d00000800000000000000050130",
         "writeInfo":{
            "bytes":624193536,
            "latency":{
               "completitionTime":{
                  "seconds":25737,
                  "nseconds":816217921
               },
               "bytesRequested":624193536,
               "opsCompleted":9526,
               "busyTime":{
                  "seconds":5,
                  "nseconds":224017937
               },
               "opsRequested":9526,
               "bytesCompleted":624193536,
               "bytesNotDelivered":0
            },
            "count":9526
         },
         "deviceId":"00000001000000000000000000000000",
         "open-stateid":"5a7a259b0000000100000004"
      }
   ]
}


you can see this with wireshark as well.

Regards,
   Tigran.
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html