Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1742749
| From | Christoph Hellwig <hch@lst.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 3/7] xfs: protect S_DAX transitions in XFS read path |
| Date | 2017-10-01 10:20 +0200 |
| Message-ID | <uvHDI-84g-5@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <utKPp-4Lc-23@gated-at.bofh.it> <utRHc-10R-19@gated-at.bofh.it> <utYIG-5O1-15@gated-at.bofh.it> <utZbI-5XL-13@gated-at.bofh.it> <uu2CD-8fI-35@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue, Sep 26, 2017 at 11:11:55AM -0700, Dan Williams wrote: > I think we'll always need an explicit override available, but yes we > need to think about what the override looks like in the context of a > kernel that is able to automatically pick the right I/O policy > relative to the media type. A potential mixed policy for reads vs > writes makes sense. Where would this finer grained I/O policy > selection go other than more inode flags? fadvise?
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
Re: [PATCH 3/7] xfs: protect S_DAX transitions in XFS read path Dan Williams <dan.j.williams@intel.com> - 2017-09-26 20:20 +0200 Re: [PATCH 3/7] xfs: protect S_DAX transitions in XFS read path Christoph Hellwig <hch@lst.de> - 2017-10-01 10:20 +0200
csiph-web