Trond Myklebust <[email protected]> wrote:
>
> The only difference I can see between the two paths is the call to
> unmap_mapping_range(). What effect would that have?
It shoots down any mapped pagecache over the affected file region. Because
the direct-io write is about to make that pagecache out-of-date. If the
application tries to use that data again it'll get a major fault and will
re-read the file contents.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
- Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
- Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
- Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
- Prev by Date:
Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
- Next by Date:
Re: PowerBook5,8 - TrackPad update
- Previous by thread:
Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
- Next by thread:
Re: infinite loop? with mmap, nfs, pwrite, O_DIRECT
- Index(es):
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]