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=-8.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SIGNED_OFF_BY,SPF_PASS,USER_AGENT_MUTT autolearn=ham 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 8C7EFC10F11 for ; Wed, 24 Apr 2019 13:35:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4752621773 for ; Wed, 24 Apr 2019 13:35:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="kXCoN4pK" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728872AbfDXNf4 (ORCPT ); Wed, 24 Apr 2019 09:35:56 -0400 Received: from mail-qt1-f195.google.com ([209.85.160.195]:46043 "EHLO mail-qt1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727517AbfDXNfz (ORCPT ); Wed, 24 Apr 2019 09:35:55 -0400 Received: by mail-qt1-f195.google.com with SMTP id b3so5353897qtc.12 for ; Wed, 24 Apr 2019 06:35:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=v/8z3MZ0pDEokogo5b6JJQQRgFo++40Z4VN8c6TpnfQ=; b=kXCoN4pKf/LixRsLbe3Ukeke3zMjueKml71rt/mxmTmoW3860P4kFel/XYzz6LzIdn Pi9fbtw3xJZ7IkUHyRKE72eP3WndXbV2vPfcnd04pYzYMbbbpufYowPmnQtzsEqNyR6A k63TQreSb1dEX5cNqsN75VwKVDZa8R+1Ye2fRhN3mVgTzU2Frk0mWe1T1y+fWdWQSe+a JRh1x9SgzSyjGAfplJqZQs3m59qajdL59dQKCnv0tht8GGDC1jxr71iWwA4f1S1Mhc7J H5t7CpMTWJ4ErhdbY7tvcXBbidinWYnZWn/ejriNQc3Ez22cDHU8MjFwVHEjgH8cPKQz 4WpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=v/8z3MZ0pDEokogo5b6JJQQRgFo++40Z4VN8c6TpnfQ=; b=UJl6G0HbnzlQY7fhk4oQVCg8RZyiE5pMNSwdBaYtMAXtK2egRmKVBXRenpBJQt/SHi O41atX2HdCHX6+GTGNVU6xSr5KWwhe5mQyAs4xmor+rFjv+6gXa+c9zhIQz46PGyfzNf 1ycuU3Nc/3tD49OvPMxJViJmIOV6vakUW0izk02XWOaQHr2M3Dr+9dkkTFdk8yQ+DXAC Y7UpAM9tnfPMZx/k01eq5aSs6ezJOZUfZ81yFVCkL36hbfIXe+Trqub9aX3FOPzXqb1Z pX0Sj5D2kRtHGg0wwKsX8ol2fdAMPXXW8C5MHiYOn3NMIwarM1TbeqUA3ni9O0zyyU9A ntsA== X-Gm-Message-State: APjAAAVKlzs3ohg3DizDG1N7Dqi1dS6WWEmZ/mvzd8LqbWesjOXRZQxy wmVHnfEM4Ge0X+g2MJ9m7h/lAA== X-Google-Smtp-Source: APXvYqyHqZNsBZ/DreApMv4QNmRDHbBhvvukBTdiQZMZm14iJL1mdeI5mWa6Dsr/Kq90yKsGCDANHA== X-Received: by 2002:ac8:24f4:: with SMTP id t49mr24699393qtt.331.1556112954599; Wed, 24 Apr 2019 06:35:54 -0700 (PDT) Received: from ziepe.ca (hlfxns017vw-156-34-49-251.dhcp-dynamic.fibreop.ns.bellaliant.net. [156.34.49.251]) by smtp.gmail.com with ESMTPSA id 25sm13693200qtw.70.2019.04.24.06.35.53 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Wed, 24 Apr 2019 06:35:53 -0700 (PDT) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1hJI41-0001ol-1T; Wed, 24 Apr 2019 10:35:53 -0300 Date: Wed, 24 Apr 2019 10:35:53 -0300 From: Jason Gunthorpe To: Leon Romanovsky Cc: Doug Ledford , RDMA mailing list , Ariel Levkovich , Eli Cohen , Mark Bloch , Saeed Mahameed , linux-netdev Subject: Re: [PATCH rdma-next 4/8] IB/mlx5: Add steering SW ICM device memory type Message-ID: <20190424133553.GF16061@ziepe.ca> References: <20190331164450.23618-1-leon@kernel.org> <20190331164450.23618-5-leon@kernel.org> <20190424130440.GA5196@ziepe.ca> <20190424131222.GG27901@mtr-leonro.mtl.com> <20190424131405.GE16061@ziepe.ca> <20190424132516.GH27901@mtr-leonro.mtl.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190424132516.GH27901@mtr-leonro.mtl.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, Apr 24, 2019 at 04:25:16PM +0300, Leon Romanovsky wrote: > On Wed, Apr 24, 2019 at 10:14:05AM -0300, Jason Gunthorpe wrote: > > On Wed, Apr 24, 2019 at 04:12:22PM +0300, Leon Romanovsky wrote: > > > On Wed, Apr 24, 2019 at 10:04:40AM -0300, Jason Gunthorpe wrote: > > > > On Sun, Mar 31, 2019 at 07:44:46PM +0300, Leon Romanovsky wrote: > > > > > From: Ariel Levkovich > > > > > > > > > > This patch adds support for allocating, deallocating and registering > > > > > a new device memory type, STEERING_SW_ICM. > > > > > This memory can be allocated and used by a privileged user for direct > > > > > rule insertion and management of the device's steering tables. > > > > > > > > > > The type is provided by the user via the dedicated attribute in > > > > > the alloc_dm ioctl command. > > > > > > > > > > Signed-off-by: Ariel Levkovich > > > > > Reviewed-by: Eli Cohen > > > > > Reviewed-by: Mark Bloch > > > > > Signed-off-by: Leon Romanovsky > > > > > drivers/infiniband/hw/mlx5/Kconfig | 2 +- > > > > > drivers/infiniband/hw/mlx5/cmd.c | 127 +++++++++++++++++++- > > > > > drivers/infiniband/hw/mlx5/cmd.h | 6 +- > > > > > drivers/infiniband/hw/mlx5/main.c | 136 +++++++++++++++++++++- > > > > > drivers/infiniband/hw/mlx5/mlx5_ib.h | 17 +++ > > > > > drivers/infiniband/hw/mlx5/mr.c | 7 ++ > > > > > include/uapi/rdma/mlx5_user_ioctl_verbs.h | 2 + > > > > > 7 files changed, 291 insertions(+), 6 deletions(-) > > > > > > > > > > diff --git a/drivers/infiniband/hw/mlx5/Kconfig b/drivers/infiniband/hw/mlx5/Kconfig > > > > > index 8d651c05de62..347d457fcb2f 100644 > > > > > +++ b/drivers/infiniband/hw/mlx5/Kconfig > > > > > @@ -1,6 +1,6 @@ > > > > > config MLX5_INFINIBAND > > > > > tristate "Mellanox 5th generation network adapters (ConnectX series) support" > > > > > - depends on NETDEVICES && ETHERNET && PCI && MLX5_CORE > > > > > + depends on NETDEVICES && ETHERNET && PCI && MLX5_CORE && PHYS_ADDR_T_64BIT > > > > > > > > Why do we need this? > > > > > > We are using phys_addr_t type and not u64 as an input to FW to emphasize > > > the caller interface, but it is different between 32 and 64 bits systems. > > > Such PHYS_ADDR_T_64BIT will ensure that phys_addr_t will be always 64 bits. > > > > ??? > > > > PHYS_ADDR_T should only ever be used to store a bus address - and if > > you are passing a bus address to/from FW then you 0 extend it on 32 > > bit, and range check on 64 bit. > > > > This is not a reason to force PHYS_ADDR_T_64BIT from a driver > > So how will I mark that we are forwarding physical address to FW? I don't know what this means.. phys_addr_t will transparently 0 extend to 64 bit which is the correct thing to do when passing a phys_addr_t to HW. Jason