From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 04DBFC433E1 for ; Fri, 3 Jul 2020 15:40:22 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D88E920899 for ; Fri, 3 Jul 2020 15:40:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593790821; bh=bJH8sQTAMxUw/Lkw2d7xfxYZAJ1Y2qMO3L8waIe/btE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=pEHf4DVLINESrJ1TIRv2/fnceQWEgnNbdiCmQ9da6f9lB9Joj6710lwLELEvtKx/b sW9d9+O1n7OTuuEXkwtYseTKAsIbd9LEn8QF+MU6RwTK4fwzikR65DedSxlA0rcBS+ 220MzrTwnOoKuzTa+/Jj42ZIf0m1VgZ6wCqiY12A= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726661AbgGCPkV (ORCPT ); Fri, 3 Jul 2020 11:40:21 -0400 Received: from mail.kernel.org ([198.145.29.99]:43282 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726152AbgGCPkS (ORCPT ); Fri, 3 Jul 2020 11:40:18 -0400 Received: from localhost (unknown [213.57.247.131]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id AD5BC2088E; Fri, 3 Jul 2020 15:40:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1593790818; bh=bJH8sQTAMxUw/Lkw2d7xfxYZAJ1Y2qMO3L8waIe/btE=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=NYOZPiUXeJGl4/tBP1/QlVEFupjVXFyEZBVaf0t7kFNNY76Hg2u1Q1WRkOqTtX6nE /AeATZgbc/Ub8AxiJRLjaCHrAWPtKnzjCK4n5fbwCtSzgKIeQizfQ3SILHKvMp1DVk nPBIr0Nc1MziPEuIZ6f4XkiomRhQVSzT0sZTYCKk= Date: Fri, 3 Jul 2020 18:40:15 +0300 From: Leon Romanovsky To: Jason Gunthorpe Cc: Doug Ledford , Feras Daoud , Jakub Kicinski , linux-rdma@vger.kernel.org, Michael Guralnik , netdev@vger.kernel.org, Saeed Mahameed Subject: Re: [PATCH rdma-next 0/2] Create IPoIB QP with specific QP number Message-ID: <20200703154015.GA696374@unreal> References: <20200623110105.1225750-1-leon@kernel.org> <20200702175541.GA721759@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200702175541.GA721759@nvidia.com> Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Jul 02, 2020 at 02:55:41PM -0300, Jason Gunthorpe wrote: > On Tue, Jun 23, 2020 at 02:01:03PM +0300, Leon Romanovsky wrote: > > From: Leon Romanovsky > > > > >From Michael, > > > > This series handles IPoIB child interface creation with setting > > interface's HW address. > > > > In current implementation, lladdr requested by user is ignored and > > overwritten. Child interface gets the same GID as the parent interface > > and a QP number which is assigned by the underlying drivers. > > > > In this series we fix this behavior so that user's requested address is > > assigned to the newly created interface. > > > > As specific QP number request is not supported for all vendors, QP > > number requested by user will still be overwritten when this is not > > supported. > > > > Behavior of creation of child interfaces through the sysfs mechanism or > > without specifying a requested address, stays the same. > > > > Thanks > > > > Michael Guralnik (2): > > net/mlx5: Enable QP number request when creating IPoIB underlay QP > > RDMA/ipoib: Handle user-supplied address when creating child > > Applied to for-next, thanks I pushed first patch. dca650991e4 net/mlx5: Enable QP number request when creating IPoIB underlay QP > > Jason