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=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 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 6F891C48BE5 for ; Mon, 21 Jun 2021 20:20:38 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 57287608FC for ; Mon, 21 Jun 2021 20:20:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231668AbhFUUWv (ORCPT ); Mon, 21 Jun 2021 16:22:51 -0400 Received: from verein.lst.de ([213.95.11.211]:43825 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231411AbhFUUWu (ORCPT ); Mon, 21 Jun 2021 16:22:50 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 1757168B05; Mon, 21 Jun 2021 22:20:34 +0200 (CEST) Date: Mon, 21 Jun 2021 22:20:33 +0200 From: Christoph Hellwig To: Jason Gunthorpe Cc: Leon Romanovsky , Doug Ledford , Avihai Horon , linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org, Christoph Hellwig , Bart Van Assche , Tom Talpey , Santosh Shilimkar , Chuck Lever III , Keith Busch , David Laight , Honggang LI , Max Gurtovoy Subject: Re: [PATCH v2 rdma-next] RDMA/mlx5: Enable Relaxed Ordering by default for kernel ULPs Message-ID: <20210621202033.GB13822@lst.de> References: <20210621180205.GA2332110@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210621180205.GA2332110@nvidia.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 21, 2021 at 03:02:05PM -0300, Jason Gunthorpe wrote: > Someone is working on dis-entangling the access flags? It took a long > time to sort out that this mess in wr.c actually does have a > distinct user/kernel call chain too.. I'd love to see it done, but I won't find time for it anytime soon.