New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
support for O_DIRECT #7155
Comments
Comment author: toolslive would you be interested in a patch ? |
Comment author: @xavierleroy O_DIRECT is Linux-specific, as far as I can see. Until now we tried hard to support only flags that are standardized e.g. in the Single Unix Specification. Is there a strong use case for O_DIRECT that would justify an exception to this rule? |
Comment author: @alainfrisch Note there is already O_SHARE_DELETE, which exists only under Windows. But again, we'd need at least on concrete use case to consider the addition. |
Comment author: toolslive The reason is that sometimes you want to write (or read) without the linux page cache caching the data. This because you know you will not be needing that data anymore in the foreseeable future. The alternative is to explain this to the page cache via fadvise. In the absence of the call, we took the fadvise route, which is simpler than to create an alternative open call (or to maintain an ocaml fork) |
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc. |
Original bug ID: 7155
Reporter: toolslive
Status: acknowledged (set by @xavierleroy on 2016-06-29T07:46:50Z)
Resolution: open
Priority: normal
Severity: feature
Version: 4.02.3
Category: standard library
Monitored by: domsj @diml
Bug description
The open_flag type in the Unix module lacks O_DIRECT.
The text was updated successfully, but these errors were encountered: