On 1/12/2016 4:58 PM, Sagi Grimberg wrote:
I didn't took the time to measure cache hit/miss. I just noticed it
a while ago and it's been bugging me for some time so I figured I'd
send it out...
The thing is that for data-path changes on high performance network
drivers, we @ least need to know that the perf is as good as it was
before the change. So you could run your iser perf IOPS test
before/after the change and post 1-2 lines with results as part of the
change-log.
I tested iser perf and it seems to sustain. I didn't see any major
difference but I really don't think block storage iops/latency is not
the correct way to evaluate this change.
maybe one nice option would be to take a look on how things are
organized in libmlx5 around that corner
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html