On 2018/1/22 23:13, Leon Romanovsky wrote: > On Mon, Jan 22, 2018 at 10:01:32PM +0800, Liuyixian (Eason) wrote: >> >> >> On 2018/1/21 14:57, Leon Romanovsky wrote: >>> On Sat, Jan 20, 2018 at 07:41:03PM +0800, Liuyixian (Eason) wrote: >>>> >>> >>> <...> >>>> >>>> With carefully release-management, there would be no compatibility problem >>>> both for hip06 and hip08. >>> >>> Sorry, for interrupting your discussion, but what does it mean "carefully >>> release-management"? >>> >>> Thanks >>> >> >> Hi Leon, >> >> Here release-management mainly means that our driver (kernel and userspace) >> for hisilicon SoC is released progressively with linux kernel versions. Take >> hip08 for example, our first version Roce driver for hip08 appear in linux >> kernel 4.14, as more and more features are added in, some features may be >> supported only in 4.16. I call this process as a release-management for >> hisilicon SoC. > > Are you aware that rdma-core and kernel are independent and can be > installed in any combinations of old/new kernel/library mix? > > Thanks > Hi Leon, Yes, I have already consider the mix case in my previous email responded to Jason. The following table illustrates our compatibility cases. +-----------------------+-------------------------------+ | | rdma-core release | | +-------------------------------+ | | release 12 | release 16 | | | (old) | (new) | +-------+---------------+---------------+---------------+ | | v4.9 | compatible | NOT compatible| |kernel | (old) | (hip06) | (hip06) | |version|---------------+---------------+---------------+ | | v4.14 | compatible | compatible | | | (new) | (hip06) | (hip06/hip08) | +-------+---------------+---------------+---------------+ The above table illustrates that old/new kernel supports old rdma-core, while the new rdma-core needs to update the kernel (driver) to new version. I think this release-management strategy is reasonable. What's your opinion? Eason -- 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
