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=-2.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, URIBL_BLOCKED,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 B16B2C282C0 for ; Tue, 22 Jan 2019 03:08:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 81F2A2085A for ; Tue, 22 Jan 2019 03:08:04 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=ziepe.ca header.i=@ziepe.ca header.b="mseg9N7g" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726887AbfAVDID (ORCPT ); Mon, 21 Jan 2019 22:08:03 -0500 Received: from mail-pl1-f196.google.com ([209.85.214.196]:40756 "EHLO mail-pl1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726823AbfAVDIC (ORCPT ); Mon, 21 Jan 2019 22:08:02 -0500 Received: by mail-pl1-f196.google.com with SMTP id u18so10718337plq.7 for ; Mon, 21 Jan 2019 19:08:02 -0800 (PST) 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=HqPV5AC+PuIGLmYKw7NuSnAgC7zHj/tg9GdynJ5Moog=; b=mseg9N7gvhHDxkVry8DxN0RPfmVMx37xqJPCTHg6y/EV6dkmxZw1oucXYeRp9H87Jc c74tGvC7wVZRpuB1u4Jao9bB4jE8aThIwG5Aoey6zrQs0kuN4ZlDFC4t7B9kBbwi4iWg W3Aegd2w4h/CFcgpsNKB+BPelerpO62w01XUAg+E2DGrx8bJ8xGgSxhLPjb+x9Lz+nc9 Yq2J7KFjlSeqOXgwOTQj+1QZlgN7TQaK9FEHQ1dA/lnPwaSDRsbRM+BXSrm9W4dMTWzq 11+FFjuLRKl9Rq3OfNcF5HbRyjGKjppEVy7YHqqkeiQPUKTIn+erTfnZaiyAO2zBBu2Y qKcA== 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=HqPV5AC+PuIGLmYKw7NuSnAgC7zHj/tg9GdynJ5Moog=; b=dHLo87IAwsPfu7ibBzx+ao2CLT8LL/2ACzXxKtGbsz0L/w/X+EffmNXhTGQFhxfydV 174+2xLoJXD0i94fBJUNCJFgMCDuOGHjdMd6BT9x05bKaJABQ1IsWUJSUBqvju0X2Rp8 eDoKBzqciqEEApZtZc29Fnyzjj9J3pmzakTLmbTxprPPpzOJfbpYDzHqxKmkNslTXYk6 QatVcY0WkQUY84wpirLl7hcrO2qXf1F8k/WnfRKZDS55tJFqINO6oVNL+j9oDPZLkLmK K8mzAnax1aBDGrw5+X/qH3zZ2i18T1PamgVqoGplhsX4Bt/am+b0aVyqU7PL7gcsGAK7 G9lA== X-Gm-Message-State: AJcUukdr0txI+BH4rGD1ndqeogLiQSiol9V5zWpm2Pxdz+ZAPNMNQ+C4 jaL/YtWizSppi57PL6DSd5HUyw== X-Google-Smtp-Source: ALg8bN7NU8RQluMU10KS+cJ5MhThYiWmuSI6UMQMhEs+/0y7sqZLwotI6D5ZMJVNmcKnrk03keHC1Q== X-Received: by 2002:a17:902:f20d:: with SMTP id gn13mr31438074plb.11.1548126482230; Mon, 21 Jan 2019 19:08:02 -0800 (PST) Received: from ziepe.ca (S010614cc2056d97f.ed.shawcable.net. [174.3.196.123]) by smtp.gmail.com with ESMTPSA id i4sm26147004pfj.82.2019.01.21.19.08.01 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 21 Jan 2019 19:08:01 -0800 (PST) Received: from jgg by mlx.ziepe.ca with local (Exim 4.90_1) (envelope-from ) id 1glmPw-0004lc-Jb; Mon, 21 Jan 2019 20:08:00 -0700 Date: Mon, 21 Jan 2019 20:08:00 -0700 From: Jason Gunthorpe To: Leon Romanovsky Cc: Doug Ledford , Leon Romanovsky , RDMA mailing list , Artemy Kovalyov , Yishai Hadas , Saeed Mahameed , linux-netdev Subject: Re: [PATCH rdma-next 0/3] Indirect MKEY over DEVX Message-ID: <20190122030800.GA18299@ziepe.ca> References: <20190113140118.10204-1-leon@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190113140118.10204-1-leon@kernel.org> 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 Sun, Jan 13, 2019 at 04:01:15PM +0200, Leon Romanovsky wrote: > From: Leon Romanovsky > > Hi, > > >From Yishai, > > This series enables using indirect mkey over DEVX. > > The first patch recognizes the creation of an indirect mkey as part of > DEVX object creation, in that case the umem valid bit shouldn't be set as > this mkey doesn't really hold a umem. > > The next two patches manage indirection mkey upon DEVX flow to support ODP. > > To support a page fault event on an indirection mkey it needs to be part > of the device mkey radix tree. Both the creation and the deletion flows for a > DEVX object which is indirection mkey were adapted to handle that. > > In addition, the page fault flow was adapted to support indirect mkey type, > it's handled in a similar flow as of the memory window mkey type. > > Yishai > > Yishai Hadas (3): > IB/mlx5: DEVX handling for indirection MKEY > IB/mlx5: Manage indirection mkey upon DEVX flow for ODP > IB/mlx5: Add support for ODP for DEVX indirection mkey applied to for-next Thanks, Jason