Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1670897
| From | Ross Zwisler <ross.zwisler@linux.intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem |
| Date | 2017-06-20 17:50 +0200 |
| Message-ID | <tUtzJ-238-43@gated-at.bofh.it> (permalink) |
| References | <tTaIN-8fC-5@gated-at.bofh.it> <tTaIN-8fC-7@gated-at.bofh.it> <tUjTI-4pJ-25@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, Jun 19, 2017 at 10:22:14PM -0700, Darrick J. Wong wrote: <> > Fourth, the VFS entry points for things like read, write, truncate, > utimes, fallocate, etc. all just bail out if S_IOMAP_FROZEN is set on a > file, so that the block map cannot be modified. mmap is still allowed, > as we've discussed. /Maybe/ we can allow fallocate to extend a file > with zeroed extents (it will be slow) as I've heard murmurs about > wanting to be able to extend a file, maybe not. Read and write should still be allowed, right?
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem "Darrick J. Wong" <darrick.wong@oracle.com> - 2017-06-20 07:30 +0200
Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem Ross Zwisler <ross.zwisler@linux.intel.com> - 2017-06-20 17:50 +0200
Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem "Darrick J. Wong" <darrick.wong@oracle.com> - 2017-06-22 09:20 +0200
Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem Dave Chinner <david@fromorbit.com> - 2017-06-22 01:40 +0200
Re: [RFC PATCH 2/2] mm, fs: daxfile, an interface for byte-addressable updates to pmem "Darrick J. Wong" <darrick.wong@oracle.com> - 2017-06-22 09:30 +0200
csiph-web