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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 25080C433FE for ; Fri, 11 Nov 2022 07:08:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232082AbiKKHIa (ORCPT ); Fri, 11 Nov 2022 02:08:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46478 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231974AbiKKHI2 (ORCPT ); Fri, 11 Nov 2022 02:08:28 -0500 Received: from out2.migadu.com (out2.migadu.com [188.165.223.204]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7AEAC79D05; Thu, 10 Nov 2022 23:08:21 -0800 (PST) Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1668150499; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=MPSyUqp5ytgKHlemveNGiW8HoPFp7nZVSiPOafehCx8=; b=A76NC/eWNNX4InK+ZKR3E0UaPtWhUIq5iLxuEtY1VRc2mqzrJoPb4oonyEHtCTfwjg43Ad jNIYVmt8Z88b6XgerlIqs6mSngEQYF/7/ra3M4ebpXjA1nUoeDNb5jm9O9A4NEvPk9fkCE whksE9ID/RrQa5CNROu44ACiIBxdNNk= Date: Fri, 11 Nov 2022 15:08:11 +0800 MIME-Version: 1.0 Subject: Re: [for-next PATCH v5 00/11] RDMA/rxe: Add RDMA FLUSH operation To: "lizhijian@fujitsu.com" , Jason Gunthorpe Cc: Bob Pearson , Leon Romanovsky , "linux-rdma@vger.kernel.org" , Zhu Yanjun , "yangx.jy@fujitsu.com" , "Yasunori Gotou (Fujitsu)" , "mbloch@nvidia.com" , "liangwenpeng@huawei.com" , "tom@talpey.com" , "tomasz.gromadzki@intel.com" , "dan.j.williams@intel.com" , "linux-kernel@vger.kernel.org" References: <20220927055337.22630-1-lizhijian@fujitsu.com> <00a3797c-9759-d4ec-6d6f-8f157cd2a220@fujitsu.com> <9fa30c8b-cb8d-efec-5896-b96177929d08@fujitsu.com> <7ee2c646-0be0-5a37-83bd-110d8a8717d7@linux.dev> <84353223-4286-10d2-c358-599ada6550f1@fujitsu.com> X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Yanjun Zhu In-Reply-To: <84353223-4286-10d2-c358-599ada6550f1@fujitsu.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT Precedence: bulk List-ID: X-Mailing-List: linux-rdma@vger.kernel.org 在 2022/11/11 14:38, lizhijian@fujitsu.com 写道: > > On 11/11/2022 14:30, Yanjun Zhu wrote: >>> After these patches, only RXE device can register *FLUSHABLE* MRs >>> successfully. If mlx try that, EOPNOSUPP will be returned. >>> >>> Similarly, Since other hardwares(MLX for example) have not supported >>> FLUSH operation, EOPNOSUPP will be returned if users try to to that. >>> >>> In short, for RXE requester, MLX responder will return error for the >>> request. MLX requester is not able to request a FLUSH operation. >> Thanks. Do you mean that FLUSH operation is only supported in RXE? ^_^ >> >> And MLX does not support FLUSH operation currently? > IMO, FLUSH and Atomic Write are newly introduced by IBA spec 1.5 > published in 2021. So hardware/drivers(MLX) should do something to > support it. Thanks. If I got you correctly, FLUSH and Atomic Write is a new feature. And from the test result, it is not supported by MLX driver currently. Wait for MLX Engineer for updates about FLUSH and Atomic Write. IMO, it had better make rxe successfully connect to one physical ib device with FLUSH and Atomic Write, such as MLX or others. Zhu Yanjun