diff options
author | Stephan Günther <[email protected]> | 2015-11-07 18:07:02 -0700 |
---|---|---|
committer | Jens Axboe <[email protected]> | 2015-11-11 09:36:56 -0700 |
commit | a310acd7a7ea53533886c11bb7edd11ffd61a036 (patch) | |
tree | 233c4cfac009f9fc03dd1817d4fa056619deaa01 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | 1fa8cc52f46c14fb1afc20c220855c40a5d28fcd (diff) |
NVMe: use split lo_hi_{read,write}q
Some controllers may require ordered split transfers even on 64bit
machines, e.g. Apple's NVMe controller as found in the MacBook8,1 and
MacBookAir7,1 (256/512GB models).
This patch enforces ordered split transfers on 64bit platforms, which
works around that issue for all controllers. As pointed out by Christoph
[1] there should be no performance impact due to that modification.
[1] http://lists.infradead.org/pipermail/linux-nvme/2015-November/002965.html
Signed-off-by: Stephan Guenther <[email protected]>
Signed-off-by: Maurice Leclaire <[email protected]>
Reviewed-by: Christoph Hellwig <[email protected]>
Updated by me to explicitly use lo_hi_read/writeq instead of playing
define tricks.
Signed-off-by: Jens Axboe <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions