On Wed, Jun 4, 2014 at 5:03 PM, Iozone <capps@xxxxxxxxxx> wrote: > Trond, > > Ok... but as the replies are coming back, all but one with EOF and zero bytes > transferred, does it still make sense to keep issuing reads that are beyond EOF ? It depends. The reads should all be sent asynchronously, so it isn't clear to me that the client will see the EOF until all the RPC requests are in flight. That said, it is true that we do not have any machinery right now to stop further submissions if we see that we have already collected enough information to complete the read() syscall. Are there any good use cases for O_DIRECT that justify adding such machinery? Oracle doesn't seem to need it. Cheers Trond > Enjoy, > Don Capps > > -----Original Message----- > From: Trond Myklebust [mailto:trond.myklebust@xxxxxxxxxxxxxxx] > Sent: Wednesday, June 04, 2014 3:42 PM > To: capps@xxxxxxxxxx > Cc: Linux NFS Mailing List > Subject: Re: FW: Forwarding request at suggestion from support > > Hi Don, > > On Wed, Jun 4, 2014 at 2:02 PM, Iozone <capps@xxxxxxxxxx> wrote: >> >> >> From: Iozone [mailto:capps@xxxxxxxxxx] >> Sent: Wednesday, June 04, 2014 11:39 AM >> To: linux-nfs@xxxxxxxxxxxxxxx >> Subject: Forwarding request at suggestion from support >> >> Dear kernel folks, >> >> Please take a look at Bugzilla bug: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1104696 >> >> Description of problem: >> >> Linux NFSv3 clients can issue extra reads beyond EOF. >> >> Condition of the test: (32KB_file is a file that is 32KB in size) >> File is being read over an NFSv3 mount. >> >> dd if=/mnt/32KB_file of=/dev/null iflag=direct bs=1M >> count=1 >> >> What one should expect over the wire: >> NFSv3_read for 32k, or NFS_read for 1M >> NFSv3_read Reply return of 32KB and EOF set. >> >> What happens with Linux NFSv3 client: >> NFSv3 read for 128k >> NFSv3 read for 128k, >> NFSv3 read for 128k, >> NFSv3 read for 128k, >> NFSv3 read for 128k, >> NFSv3 read for 128k, >> NFSv3 read for 128k, >> NFSv3 read for 128k. >> followed by: >> NFSv3 read reply of 32k, >> NFSv3 read reply of 0, >> NFSv3 read reply of 0, >> NFSv3 read reply of 0, >> NFSv3 read reply of 0, >> NFSv3 read reply of 0, >> NFSv3 read reply of 0, >> NFSv3 read reply of 0. >> >> So… instead of a single round trip with a short read length returned, >> there were 8 async I/O ops sent to the NFS server, and 8 replies from >> the NFS server. >> The client knew the file size before even sending the very first >> request, but went ahead and issued an large number of reads that it >> should have known were beyond EOF. >> >> This client behavior hammers NFS servers with requests that are >> guaranteed to always fail, and burn CPU cycles, for operations that it >> knew were pointless. >> >> While the application is getting correct answers to the API calls, the >> poor client and server are beating each other senseless over the wire. >> >> NOTE: This only happens if O_DIRECT is being used… (thus the >> iflag=direct) > > Yes. This behaviour is intentional in the case of O_DIRECT. The reason why we should not change it is that we don't ever want to rely on cached values for the file size when doing uncached I/O. > An application such as Oracle may have out-of-band information about writes to the file that were made by another client directly to the server, in which case it would be wrong for the kernel to truncate those reads based on its cached information. > > Cheers > Trond > > -- > Trond Myklebust > > Linux NFS client maintainer, PrimaryData > > trond.myklebust@xxxxxxxxxxxxxxx > -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- 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
