{"push_id":898956454,"size":1,"distinct_size":1,"ref":"refs/heads/svn_head","head":"7deacf1774c54c21361212b184a34eeb7a336682","before":"0bb5d4d432c8013f5b80ed43bb173f02fe8a63f8","commits":[{"sha":"7deacf1774c54c21361212b184a34eeb7a336682","author":{"email":"1d9431876282b4e6e985e9a66c7d02d03813e37d@ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f","name":"smh"},"message":"Limit stripesize reported from nvd(4) to 4K\n\nIntel NVMe controllers have a slow path for I/Os that span a 128KB stripe boundary but ZFS limits ashift, which is derived from d_stripesize, to 13 (8KB) so we limit the stripesize reported to geom(8) to 4KB.\n\nThis may result in a small number of additional I/Os to require splitting in nvme(4), however the NVMe I/O path is very efficient so these additional I/Os will cause very minimal (if any) difference in performance or CPU utilisation.\n\nThis can be controller by the new sysctl kern.nvme.max_optimal_sectorsize.\n\nMFC after:\t1 week\nSponsored by:\tMultiplay\nDifferential Revision:\thttps://reviews.freebsd.org/D4446\n\n\ngit-svn-id: svn+ssh://svn.freebsd.org/base/head@292074 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f","distinct":true,"url":"https://api.github.com/repos/freebsd/freebsd/commits/7deacf1774c54c21361212b184a34eeb7a336682"}]}