{"action":"created","issue":{"url":"https://api.github.com/repos/danburkert/mmap/issues/3","labels_url":"https://api.github.com/repos/danburkert/mmap/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/danburkert/mmap/issues/3/comments","events_url":"https://api.github.com/repos/danburkert/mmap/issues/3/events","html_url":"https://github.com/danburkert/mmap/issues/3","id":95082927,"number":3,"title":"Support for msync","user":{"login":"posix4e","id":806363,"avatar_url":"https://avatars.githubusercontent.com/u/806363?v=3","gravatar_id":"","url":"https://api.github.com/users/posix4e","html_url":"https://github.com/posix4e","followers_url":"https://api.github.com/users/posix4e/followers","following_url":"https://api.github.com/users/posix4e/following{/other_user}","gists_url":"https://api.github.com/users/posix4e/gists{/gist_id}","starred_url":"https://api.github.com/users/posix4e/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/posix4e/subscriptions","organizations_url":"https://api.github.com/users/posix4e/orgs","repos_url":"https://api.github.com/users/posix4e/repos","events_url":"https://api.github.com/users/posix4e/events{/privacy}","received_events_url":"https://api.github.com/users/posix4e/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-07-15T01:42:28Z","updated_at":"2015-07-15T04:53:44Z","closed_at":null,"body":"There's no reason to flush all outstanding changes in all cases. It might be nice if we supported msync"},"comment":{"url":"https://api.github.com/repos/danburkert/mmap/issues/comments/121487198","html_url":"https://github.com/danburkert/mmap/issues/3#issuecomment-121487198","issue_url":"https://api.github.com/repos/danburkert/mmap/issues/3","id":121487198,"user":{"login":"posix4e","id":806363,"avatar_url":"https://avatars.githubusercontent.com/u/806363?v=3","gravatar_id":"","url":"https://api.github.com/users/posix4e","html_url":"https://github.com/posix4e","followers_url":"https://api.github.com/users/posix4e/followers","following_url":"https://api.github.com/users/posix4e/following{/other_user}","gists_url":"https://api.github.com/users/posix4e/gists{/gist_id}","starred_url":"https://api.github.com/users/posix4e/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/posix4e/subscriptions","organizations_url":"https://api.github.com/users/posix4e/orgs","repos_url":"https://api.github.com/users/posix4e/repos","events_url":"https://api.github.com/users/posix4e/events{/privacy}","received_events_url":"https://api.github.com/users/posix4e/received_events","type":"User","site_admin":false},"created_at":"2015-07-15T04:53:44Z","updated_at":"2015-07-15T04:53:44Z","body":"       According to POSIX, either MS_SYNC or MS_ASYNC  must  be  specified  in\r\n       flags,  and  indeed  failure  to  include one of these flags will cause\r\n       msync() to fail on some systems.  However,  Linux  permits  a  call  to\r\n       msync()  that specifies neither of these flags, with semantics that are\r\n       (currently) equivalent to specifying MS_ASYNC.   (Since  Linux  2.6.19,\r\n       MS_ASYNC  is  in  fact  a no-op, since the kernel properly tracks dirty\r\n       pages and flushes them to storage as necessary.)   Notwithstanding  the\r\n       Linux  behavior, portable, future-proof applications should ensure that\r\n       they specify either MS_SYNC or MS_ASYNC in flags.\r\n"}}