Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1418183
| From | Christoph Hellwig <hch@infradead.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io |
| Date | 2016-06-09 11:10 +0200 |
| Message-ID | <rI48p-4md-1@gated-at.bofh.it> (permalink) |
| References | <rG5Lj-AU-11@gated-at.bofh.it> <rG5Lj-AU-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Jun 03, 2016 at 06:28:17PM -0400, Waiman Long wrote: > Since all the DAX I/Os are synchronous, there is no need to update > the DIO count in dax_do_io() when the count has already been updated > or the i_rwsem lock (read or write) has or will be taken. > > This patch passes in the DIO_SKIP_DIO_COUNT flag to dax_do_io() to > disable two unneeded atomic operations that can slow thing down in > fast storages like NVDIMM. > > With a 38-threads fio I/O test with 2 shared files (on DAX-mount ext4 > formatted NVDIMM) running on a 4-socket Haswell-EX server with 4.6-rc1 > kernel, the aggregated bandwidths before and after the patch were: Please do the right thing and remove the code to call inode_dio_begin / inode_dio_end entirely. There is nothing ext4 specific about the dax code being synchronous. Together with my previous suggestion that also allows dropping the flags argument. Then as a next step remove the end_io argument and just call it in the callers which is perfectly safe again as dax is synchronous.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io Waiman Long <Waiman.Long@hpe.com> - 2016-06-04 00:30 +0200 Re: [PATCH 3/3] ext4: Pass DIO_SKIP_DIO_COUNT to dax_do_io Christoph Hellwig <hch@infradead.org> - 2016-06-09 11:10 +0200
csiph-web