Bug 1523094 - to detect EOF, avoid sending readv fop to backend when offset is within byte range of file size
Summary: to detect EOF, avoid sending readv fop to backend when offset is within byte ...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: GlusterFS
Classification: Community
Component: quick-read
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Milind Changire
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-07 08:32 UTC by Milind Changire
Modified: 2019-06-20 05:12 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-06-20 05:12:20 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.