Bug 850666
Summary: | [RFE] RHS 2.0 Plus Feature Documentation: O_DIRECT Support in Translators | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Divya <divya> |
Component: | doc-Administration_Guide | Assignee: | Divya <divya> |
Status: | CLOSED NOTABUG | QA Contact: | Gowrishankar Rajaiyan <grajaiya> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | unspecified | CC: | amarts, asriram, gluster-bugs, grajaiya, mhideo, storage-doc, vbellur, vinaraya |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Following improvements have been done regarding O_DIRECT:
1) Improved write-behind translator to perform better with O_DIRECT.
2) Filter O_DIRECT on the clients to avoid sending the flag over the wire to servers.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-19 07:18:10 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: | |||
Bug Depends On: | 845213, 856156, 857673 | ||
Bug Blocks: |
Description
Divya
2012-08-22 06:30:10 UTC
Hi Amar, Could you please provide O_Direct support information in Doc Text field? Thanks, Divya Vijay, I have added doc_text field, please verify if its fine. Amar, Seeking clarification on this bug. Based on our earlier conversation, you had mentioned that this bug does not have any impact on docs. Kindly elaborate and clarify. Your clarification would help me resolve the bug. Regards, Divya Hi Divya, after discussions, we understood mention about O_DIRECT is not for any benefits of user, and it is very much a technical detail about the product, which it *should* handle. So, there is no need to elaborate on this option. Hope this clarifies your doubts. As per Amar's comment, this feature does not have documentation impact. Hence, closing this bug. |