All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Liuyixian (Eason)" <liuyixian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-core 2/2] libhns: Support cq record doorbell
Date: Sat, 20 Jan 2018 19:41:03 +0800	[thread overview]
Message-ID: <68e02f2a-0474-bc73-a784-fd52dbbde552@huawei.com> (raw)
In-Reply-To: <20180119200029.GD3437-uk2M96/98Pc@public.gmane.org>



On 2018/1/20 4:00, Jason Gunthorpe wrote:
> On Fri, Jan 19, 2018 at 07:04:42PM +0800, Liuyixian (Eason) wrote:
> 
>> For case 1, the new kernel driver can't support old user application or old userspace driver.
>> Because we use the record db solution (what this patchset does and why add new db_addr in kernel)
>> to substitute with operating register, which used by the old userspace driver.
>> Therefore, users need to update the userspace driver to the version which support record db.
> 
> This is not acceptable for the kernel. You must maintain compatability
> with old userspace.
> 
> Also, new userspace must work with older kernels.
> 
> Jason

Hi Jason,

Maybe my previous email caused some confusions to people.
Let me illustrate the compatibility more clear.

For hip06, which not support record db, even while it creates cq in userspace
with hns_roce_create_cq (db_addr already there), it will do nothing with db_addr.
The kernel also will not access db_addr, both for old kernel and new kernel(adding db_addr).
Because hip06 pushes db by operating register, this manner keeps unchanged.
Thus, the old/new kernel support both old/new userspace for hip06,

For hip08, which is still under development to support record db, considering
forward compatibility that new kernel with old userspace, as old userspace operates
register and new kernel still provide those registers, there is no forward compatibility
problem. The reverse (backward compatibility) is not true. It is not possible to take
new userspace will still run correctly if the kernel is old. As new userspace use
db_addr substitute operating register, it can run correctly only on new kernel
(the patchset goes with this patchset submitted to for-next) and later kernel versions.
I think it is reasonable for this case.

With carefully release-management, there would be no compatibility problem
both for hip06 and hip08.

Eason

> 
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-01-20 11:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18  2:35 [PATCH rdma-core 0/2] Support rq and cq record doorbell Yixian Liu
     [not found] ` <1516242961-154453-1-git-send-email-liuyixian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-18  2:36   ` [PATCH rdma-core 1/2] libhns: Support rq " Yixian Liu
2018-01-18  2:36   ` [PATCH rdma-core 2/2] libhns: Support cq " Yixian Liu
     [not found]     ` <1516242961-154453-3-git-send-email-liuyixian-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-18  4:37       ` Jason Gunthorpe
     [not found]         ` <20180118043717.GC8414-uk2M96/98Pc@public.gmane.org>
2018-01-18  7:25           ` Liuyixian (Eason)
     [not found]             ` <9e577314-4fcb-45de-6909-d5b3be570196-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-18 16:19               ` Jason Gunthorpe
     [not found]                 ` <20180118161949.GA18973-uk2M96/98Pc@public.gmane.org>
2018-01-19 11:04                   ` Liuyixian (Eason)
     [not found]                     ` <a33a1337-665f-4cd4-5b39-b12d9f03af72-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-19 20:00                       ` Jason Gunthorpe
     [not found]                         ` <20180119200029.GD3437-uk2M96/98Pc@public.gmane.org>
2018-01-20 11:41                           ` Liuyixian (Eason) [this message]
     [not found]                             ` <68e02f2a-0474-bc73-a784-fd52dbbde552-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-20 16:46                               ` Jason Gunthorpe
     [not found]                                 ` <20180120164625.GA14372-uk2M96/98Pc@public.gmane.org>
2018-01-23 12:51                                   ` Liuyixian (Eason)
     [not found]                                     ` <124fa0b2-ac35-a103-205b-252fddea2665-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-23 15:04                                       ` Jason Gunthorpe
     [not found]                                         ` <20180123150421.GA30670-uk2M96/98Pc@public.gmane.org>
2018-01-24 10:35                                           ` Liuyixian (Eason)
     [not found]                                             ` <91b5f324-cfaf-e778-2d6c-46000267f2cb-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-24 11:51                                               ` Leon Romanovsky
     [not found]                                                 ` <20180124115141.GG1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-24 16:30                                                   ` Jason Gunthorpe
     [not found]                                                     ` <20180124163056.GC16845-uk2M96/98Pc@public.gmane.org>
2018-01-25 13:16                                                       ` Liuyixian (Eason)
2018-01-21  6:57                               ` Leon Romanovsky
     [not found]                                 ` <20180121065727.GF1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-22 14:01                                   ` Liuyixian (Eason)
     [not found]                                     ` <1d95b4da-1cb8-e1ef-9c0e-4ac70a848d38-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-01-22 15:13                                       ` Leon Romanovsky
     [not found]                                         ` <20180122151307.GK1393-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2018-01-23 12:38                                           ` Liuyixian (Eason)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=68e02f2a-0474-bc73-a784-fd52dbbde552@huawei.com \
    --to=liuyixian-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=jgg-uk2M96/98Pc@public.gmane.org \
    --cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.