You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 22, 2023. It is now read-only.
I suppose that it should be pmem.map_file, which seems to be similar (https://pynvm.readthedocs.io/en/v0.3.1/pmem.html#nvm.pmem.map_file). However, the documentation for map_file only explains three of the four parameters, and they are all needed (that is what I see in Python 2.7 and pynvm==0.3.1, which is my current environment).
I am unable to execute the tests nor I fully understand the meaning of the mode parameter. I don't know if this is only a documentation problem or the call is expected to have optional parameters.
The text was updated successfully, but these errors were encountered:
I just saw that map_file call expects a name of file, not a fallocate result, so I am more confused. Does this superseed the previous approach fallocate + map? Or is it completely different?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The current examples in https://pynvm.readthedocs.io/en/v0.3.1/getting_started.html regarding
libpmem
library use a callpmem.map
which doesn't seem to exist.I suppose that it should be
pmem.map_file
, which seems to be similar (https://pynvm.readthedocs.io/en/v0.3.1/pmem.html#nvm.pmem.map_file). However, the documentation formap_file
only explains three of the four parameters, and they are all needed (that is what I see in Python 2.7 and pynvm==0.3.1, which is my current environment).I am unable to execute the tests nor I fully understand the meaning of the
mode
parameter. I don't know if this is only a documentation problem or the call is expected to have optional parameters.The text was updated successfully, but these errors were encountered: