From: Leon Romanovsky <leon@kernel.org>
To: Cheng Xu <chengyou@linux.alibaba.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org, KaiShen@linux.alibaba.com
Subject: Re: [PATCH for-next 4/4] RDMA/erdma: Support dynamic mtu
Date: Wed, 21 Sep 2022 10:35:55 +0300 [thread overview]
Message-ID: <Yyq+24CUolthp2lo@unreal> (raw)
In-Reply-To: <4f2425e1-4326-c337-5bc5-06400a6cce62@linux.alibaba.com>
On Wed, Sep 21, 2022 at 10:28:57AM +0800, Cheng Xu wrote:
>
>
> On 9/20/22 7:32 PM, Leon Romanovsky wrote:
> > On Fri, Sep 09, 2022 at 05:38:22PM +0800, Cheng Xu wrote:
> >> Hardware now support jumbo frame for RDMA. So we introduce a new CMDQ
> >> message to support mtu change notification.
> >>
> <...>
> >
> > I don't see any backward compatibility here. How can you make sure that
> > new code that supports MTU change works correctly on old FW/device?
> >
>
> In this case, driver needn't to consider backward compatibility.
>
> ERDMA hardware is programmable part of our iaas infrastructure, and can be
> hot-update without BMs/VMs awareness.Before I submitted this patch, all the
> FWs has been updated, and support this feature, no old FWs exist.
I'm not big fan of such answers, but ok, applied.
>
> Thanks,
> Cheng Xu
>
>
next prev parent reply other threads:[~2022-09-21 7:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 9:38 [PATCH for-next 0/4] RDMA/erdma: cleanups and updates 9-9-2022 Cheng Xu
2022-09-09 9:38 ` [PATCH for-next 1/4] RDMA/erdma: Eliminate unnecessary casting for erdma_post_cmd_wait Cheng Xu
2022-09-09 9:38 ` [PATCH for-next 2/4] RDMA/erdma: Remove redundant includes Cheng Xu
2022-09-09 9:38 ` [PATCH for-next 3/4] RDMA/erdma: Make hardware internal opcodes invisible to driver Cheng Xu
2022-09-09 9:38 ` [PATCH for-next 4/4] RDMA/erdma: Support dynamic mtu Cheng Xu
2022-09-20 11:32 ` Leon Romanovsky
2022-09-21 2:28 ` Cheng Xu
2022-09-21 7:35 ` Leon Romanovsky [this message]
2022-09-21 7:32 ` (subset) " Leon Romanovsky
2022-09-20 11:33 ` [PATCH for-next 0/4] RDMA/erdma: cleanups and updates 9-9-2022 Leon Romanovsky
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=Yyq+24CUolthp2lo@unreal \
--to=leon@kernel.org \
--cc=KaiShen@linux.alibaba.com \
--cc=chengyou@linux.alibaba.com \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.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.