On 08/25/2017 07:46 PM, Rebecca Cran wrote: > I'm not sure how far we want to get into optimizing fio for specific CPUs? > > I've done some testing and found that when running the mmap ioengine > against an NVDIMM-N on a modern Intel CPU I can gain a few hundred MB/s > by optimizing the memory copy using avx/avx2 versus the system's memcpy > implementation. > > > Should I proceed with submitting a patch, or do we want to avoid getting > into these sort of optimizations? If we can do it cleanly, that's fine. See for instance how we detect presence of crc32c hw assist at init time. For memcpy(), the libc functions should really be doing this, however. That said, let's see a patch, it's easier to discuss concrete patches than just ideas. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
