All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Yonatan Nachum <ynachum@amazon.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next] RDMA/efa: Add checksum support for admin responses
Date: Mon, 13 Apr 2026 22:08:09 +0300	[thread overview]
Message-ID: <20260413190809.GO21470@unreal> (raw)
In-Reply-To: <20260413092130.GA18233@dev-dsk-ynachum-1b-aa121316.eu-west-1.amazon.com>

On Mon, Apr 13, 2026 at 09:21:30AM +0000, Yonatan Nachum wrote:
> On Mon, Apr 13, 2026 at 11:35:15AM +0300, Leon Romanovsky wrote:
> > On Thu, Apr 09, 2026 at 07:49:05AM +0000, Yonatan Nachum wrote:
> > > EFA devices added support for CRC16 checksum on admin responses and to
> > > expose it to the driver the API version increased to 0.2. Add a check
> > > for support on device init and if supported validate the checksum on
> > > each admin response the driver receives. If the checksum validation
> > > failed, drop the CQE.
> > > 
> > > Add the CRC16 module to Kconfig to have the in-tree dependency.
> > > 
> > > Reviewed-by: Firas Jahjah <firasj@amazon.com>
> > > Reviewed-by: Michael Margolin <mrgolin@amazon.com>
> > > Signed-off-by: Yonatan Nachum <ynachum@amazon.com>
> > > ---
> > >  drivers/infiniband/hw/efa/Kconfig             |  3 +-
> > >  .../infiniband/hw/efa/efa_admin_cmds_defs.h   |  3 --
> > >  drivers/infiniband/hw/efa/efa_admin_defs.h    | 15 +++---
> > >  drivers/infiniband/hw/efa/efa_com.c           | 50 ++++++++++++++++---
> > >  drivers/infiniband/hw/efa/efa_com.h           |  4 +-
> > >  5 files changed, 55 insertions(+), 20 deletions(-)
> > 
> > <...>
> > 
> > > -#define EFA_ADMIN_API_VERSION_MAJOR          0
> > > -#define EFA_ADMIN_API_VERSION_MINOR          1
> > 
> > <...>
> > 
> > > +#define EFA_ADMIN_API_VERSION_MAJOR          0
> > > +#define EFA_ADMIN_API_VERSION_MINOR          2
> > 
> > <...>
> > 
> > > @@ -954,16 +990,16 @@ int efa_com_validate_version(struct efa_com_dev *edev)
> > >  		  EFA_GET(&ver, EFA_REGS_VERSION_MAJOR_VERSION),
> > >  		  EFA_GET(&ver, EFA_REGS_VERSION_MINOR_VERSION));
> > >  
> > > -	EFA_SET(&min_ver, EFA_REGS_VERSION_MAJOR_VERSION,
> > > -		EFA_ADMIN_API_VERSION_MAJOR);
> > > -	EFA_SET(&min_ver, EFA_REGS_VERSION_MINOR_VERSION,
> > > -		EFA_ADMIN_API_VERSION_MINOR);
> > > +	EFA_SET(&min_ver, EFA_REGS_VERSION_MAJOR_VERSION, EFA_MIN_ADMIN_API_VERSION_MAJOR);
> > > +	EFA_SET(&min_ver, EFA_REGS_VERSION_MINOR_VERSION, EFA_MIN_ADMIN_API_VERSION_MINOR);
> > >  	if (ver < min_ver) {
> > >  		ibdev_err(edev->efa_dev,
> > >  			  "EFA version is lower than the minimal version the driver supports\n");
> > >  		return -EOPNOTSUPP;
> > >  	}
> > 
> > This change breaks all backward compatibility. Are you certain that every EFA
> > device is running the correct firmware, including those currently deployed and
> > used by customers? If not, they will stop to work after random kernel update.
> > 
> > Thanks
> 
> The minimum required API version for the driver to load remains 0.1
> (EFA_MIN_ADMIN_API_VERSION_MINOR). The CRC16 checksum validation is only
> enabled when the device reports API version >= 0.2. Devices running
> firmware 0.1 will continue to work — they just won't have checksum
> validation on admin responses.

Ahh, yes, I missed the addition of _MIN_ in the name.

Thanks

> 

  reply	other threads:[~2026-04-13 19:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-09  7:49 [PATCH for-next] RDMA/efa: Add checksum support for admin responses Yonatan Nachum
2026-04-13  8:35 ` Leon Romanovsky
2026-04-13  9:21   ` Yonatan Nachum
2026-04-13 19:08     ` Leon Romanovsky [this message]
2026-04-20  6:55 ` Yonatan Nachum
2026-04-23 12:06   ` Leon Romanovsky
2026-05-11  8:06 ` 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=20260413190809.GO21470@unreal \
    --to=leon@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=ynachum@amazon.com \
    /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.