On 12 April 2018 at 16:22, Jan Kara <j...@suse.cz> wrote:
> Hello Michael!
> On Thu 12-04-18 15:00:49, Michael Kerrisk (man-pages) wrote:
>> Hello Jan,
>> I have applied your patch, and tweaked the text a little, and pushed
>> the result to the git repo.
>> > +.B MAP_SHARED
>> > +type will silently ignore this flag.
>> > +This flag is supported only for files supporting DAX (direct mapping of
>> > persistent
>> > +memory). For other files, creating mapping with this flag results in
>> > +.B EOPNOTSUPP
>> > +error. Shared file mappings with this flag provide the guarantee that
>> > while
>> > +some memory is writeably mapped in the address space of the process, it
>> > will
>> > +be visible in the same file at the same offset even after the system
>> > crashes or
>> > +is rebooted. This allows users of such mappings to make data modifications
>> > +persistent in a more efficient way using appropriate CPU instructions.
>> It feels like there's a word missing/unclear wording in the previous
>> line, before "using". Without that word, the sentence feels a bit
>> Should it be:
>> persistent in a more efficient way *through the use of* appropriate
>> CPU instructions.
>> persistent in a more efficient way *than using* appropriate CPU instructions.
>> Is suspect the first is correct, but need to check.
> Yes, the first is correct.
Thanks for both checking that phrasing. In the end I decided to reword
the sentence a bot more substantially:
In conjunction with the use of appropriate CPU
instructions, this provides users of such mappings
with a more efficient way of making data modifica‐
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
Linux-nvdimm mailing list