Bug 1523094

Summary:	to detect EOF, avoid sending readv fop to backend when offset is within byte range of file size
Product:	[Community] GlusterFS	Reporter:	Milind Changire <mchangir>
Component:	quick-read	Assignee:	Milind Changire <mchangir>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	atumball, bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-20 05:12:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Milind Changire 2017-12-07 08:32:23 UTC

Description of problem:
currently, a readv fop is forwarded to brick backend to detect EOF

Expected results:
with quick-read turned "on" and the file contents cached, the EOF detection should take place at the client end and should not be incur a network hop to the back-end file system.

Comment 1 Worker Ant 2017-12-07 08:35:17 UTC

REVIEW: https://review.gluster.org/18982 (performance/quick-read: don't send a readv to backend to identify EOF) posted (#1) for review on master by Milind Changire

Comment 2 Amar Tumballi 2019-06-20 05:12:20 UTC

marking as DEFERRED to indicate the status. Will revisit it after couple of months.