From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 70D80A0C41 for ; Wed, 23 Jun 2021 15:51:52 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0FD814003E; Wed, 23 Jun 2021 15:51:52 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id 20DB64003E for ; Wed, 23 Jun 2021 15:51:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1624456309; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=NJceAk+blw8RK1ITKCZOMIegZyfMxV/hiF6ijN7l6FQ=; b=Rdsi3DBMua+iRCQCK0v+AJax7E4w4qX7qOBB/Lysf+/K6zUwMTsDQA0hS2esV6PHE3u3b6 kvvNHU67UgxL0WQOsf/0S7yvYLsL4RkYxs9Y5P4acfZG/u3RjLVC07zKgGwYzI2DxA1/Pc GdLGBmpdy/IYAk3anWpw0mORNJOwL8Y= Received: from mail-vs1-f70.google.com (mail-vs1-f70.google.com [209.85.217.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-335-X4Td7GopObWCwv4QoO1JyQ-1; Wed, 23 Jun 2021 09:51:48 -0400 X-MC-Unique: X4Td7GopObWCwv4QoO1JyQ-1 Received: by mail-vs1-f70.google.com with SMTP id l124-20020a6770820000b029025d866a613cso382605vsc.11 for ; Wed, 23 Jun 2021 06:51:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NJceAk+blw8RK1ITKCZOMIegZyfMxV/hiF6ijN7l6FQ=; b=eE34qekvIMUcBJpUM/nIZAE2s5PbaTv5JhGO0bddnQqyQwJfMrBX3iCSqMWxLU+n6P AbIPboQyogWFjx9DmQozGY84sFT1+YYssFrOW1tyweSgcxqlEV8NNSld+GfxB3fsxBiU 8ATGs8pYVMe3qG+H53dQ58ZdsFZiiYRdA66rhv4SnsHcsbKbzvA3jUBBh6occl4aZdy+ XffAZ5nju2A9hqptS/hHeTwJzx6HgJjS4+YvamZQaXFR2ScFszEF9yxd43wLMieDury1 EYK+/RVi0jnDY4f2Aee6gMgWffw6X+e1Xrigr2VC1iOpxt+be0tRbgoCkDU50XbZGZPF 98ow== X-Gm-Message-State: AOAM531ifSM4vRDOBXW4NCB2IJojgvD83DeCfDtaG0urzO9srVOuZQ0/ DN62l434SisynNLoK6C5vhS+euCslPc/Gw15i8g2ohZJAtDq0kpzYTRV2xm+APD/1DnZI9tapCI OiSG5Bk5sXieoJAPwd69XK94= X-Received: by 2002:a67:fe90:: with SMTP id b16mr135100vsr.5.1624456307531; Wed, 23 Jun 2021 06:51:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxxy3iBFxvTcGvhs6PzPgzKqz2GkVgN3yfTTGmnTyXyxb+9qD2OLMxYp9WMbGz45Zq23f7wcnP46JW+AfCLuoE= X-Received: by 2002:a67:fe90:: with SMTP id b16mr135076vsr.5.1624456307325; Wed, 23 Jun 2021 06:51:47 -0700 (PDT) MIME-Version: 1.0 References: <20210619124830.25297-1-viacheslavo@nvidia.com> In-Reply-To: From: David Marchand Date: Wed, 23 Jun 2021 15:51:35 +0200 Message-ID: To: Slava Ovsiienko Cc: dev , Raslan Darawsheh , Matan Azrad , NBU-Contact-Thomas Monjalon , dpdk stable Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2] common/mlx5: add provider query port support to glue library X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On Wed, Jun 23, 2021 at 1:27 PM Slava Ovsiienko wrote: > > > This patch is highly desirable to be provided in DPDK LTS releases due > > > to it covers the major compatibility issue. > > > > This patch is a fix, yet nothing tells this story in the title. > > This patch is not a fix. Actually it covers the compatibility issue, not a bug. I still think it counts as a fix in the sense that the mlx5 driver behavior changes to an undesired state if rdma-core gets updated. It's not about preferring "fix" in the title. It is more accurate/descriptive to me. If you feel strongly against "fix", I won't insist. Yet "add provider quer port support to glue library" is just black magic to most of us. > The Upstream rdma-core was evolved, its community adopted a > slightly different API version than was presented in the vendor version. > Our PMD should conform both versions and we provided this patch for DPDK. Let's try differently. Place yourself as someone who does not know a thing about the mlx5 driver and rdma-core. How does such a person understand the impact of this patch? I would state in the title that the mlx5 driver can now handle correctly rdma-core 35. Additionally, it could indicate which feature X is now behaving as intended. But if feature X is something internal to the mlx5 driver, it is worth skipping. -- David Marchand