On 6/10/2015 4:26 AM, Christoph Lameter wrote:
>I have no problem with a bare metal interface exposing this. But pretendin=
>g that it's generic and that this is the one and only way that this could b=
>e implemented doesn't make it so.
This is a way it was implemented and its usable. Shooting for pie in the
sky does not bring us anything. Nor ideas of requirements from a new
experimental API that does not support the basic features that we need
and seems to be on its way to mess up the latencies of access to RDMA
operations.
Doug,
What's your maintainer say here?
The current proposal has:
1. raw HCA clock completion generation time-stamp for CQEs
2. HCA clock frequency in KHZ
3. mask telling how many bits are relevant from the 64bit time-stamp
This is fairly simple, practical and very much usable to FSI
applications and users, and can be extended later if someone comes up
with better/other combination of the frequency/mask. Have a GO?
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
