From: Cheng Xu <chengyou@linux.alibaba.com>
To: Zhu Yanjun <yanjun.zhu@linux.dev>,
Boshi Yu <boshiyu@linux.alibaba.com>,
jgg@ziepe.ca, leon@kernel.org
Cc: linux-rdma@vger.kernel.org, kaishen@linux.alibaba.com
Subject: Re: [PATCH for-next 1/8] RDMA/erdma: Probe the erdma RoCEv2 device
Date: Thu, 28 Nov 2024 10:07:42 +0800 [thread overview]
Message-ID: <765311dd-16d5-28f3-cdda-93578e5f40eb@linux.alibaba.com> (raw)
In-Reply-To: <e03c5cf0-f4dc-41c2-af48-a95463592eed@linux.dev>
On 11/26/24 11:36 PM, Zhu Yanjun wrote:
> 在 2024/11/26 7:59, Boshi Yu 写道:
>> Currently, the erdma driver supports both the iWARP and RoCEv2 protocols.
>> The erdma driver reads the ERDMA_REGS_DEV_PROTO_REG register to identify
>> the protocol used by the erdma device. Since each protocol requires
>> different ib_device_ops, we introduce the erdma_device_ops_iwarp and
>> erdma_device_ops_rocev2 for iWARP and RoCEv2 protocols, respectively.
>>
> Hi, Boshi
>
> From alomost all of the RDMA users, it seems that RoCEv2 protocol is required while very few users request iWARP protocol in their production hosts. But in the erdma HW/FW, this iWARP protocol is supported. Is this iWARP protocol for some special use cases in the Ali-Cloud environment?
>
Hi, Yanjun,
iWarp & TCP have some good features, such as Tail Loss Probe(TLP), selective ACK and
out-of-order DDP, so that can get better performance in large-scale lossy network. The
current usage scenarios include HPC industrial simulation, redis, PolarDB and big data
in public cloud environment.
Thanks,
Cheng Xu
> I am just curious about this, not to be against this patch series. If this is related with the Ali-Cloud security, you can ignore this.
>
> Thanks,
> Zhu Yanjun
>
next prev parent reply other threads:[~2024-11-28 2:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 6:59 [PATCH for-next 0/8] RDMA/erdma: Support the RoCEv2 protocol Boshi Yu
2024-11-26 6:59 ` [PATCH for-next 1/8] RDMA/erdma: Probe the erdma RoCEv2 device Boshi Yu
2024-11-26 15:36 ` Zhu Yanjun
2024-11-28 2:07 ` Cheng Xu [this message]
2024-11-28 13:07 ` Zhu Yanjun
2024-12-04 14:03 ` Leon Romanovsky
2024-12-05 2:46 ` Boshi Yu
2024-11-26 6:59 ` [PATCH for-next 2/8] RDMA/erdma: Add GID table management interfaces Boshi Yu
2024-11-26 15:51 ` Zhu Yanjun
2024-11-28 2:35 ` Boshi Yu
2024-11-29 8:54 ` Zhu Yanjun
2024-11-29 11:18 ` Boshi Yu
2024-11-29 18:40 ` Zhu Yanjun
2024-11-26 6:59 ` [PATCH for-next 3/8] RDMA/erdma: Add the erdma_query_pkey() interface Boshi Yu
2024-11-26 6:59 ` [PATCH for-next 4/8] RDMA/erdma: Add address handle implementation Boshi Yu
2024-12-04 14:11 ` Leon Romanovsky
2024-12-05 2:54 ` Boshi Yu
2024-11-26 6:59 ` [PATCH for-next 5/8] RDMA/erdma: Add erdma_modify_qp_rocev2() interface Boshi Yu
2024-11-26 6:59 ` [PATCH for-next 6/8] RDMA/erdma: Reformat the code of the modify_qp interface Boshi Yu
2024-11-26 6:59 ` [PATCH for-next 7/8] RDMA/erdma: Add the query_qp command to the cmdq Boshi Yu
2024-11-26 6:59 ` [PATCH for-next 8/8] RDMA/erdma: Support UD QPs and UD WRs Boshi Yu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=765311dd-16d5-28f3-cdda-93578e5f40eb@linux.alibaba.com \
--to=chengyou@linux.alibaba.com \
--cc=boshiyu@linux.alibaba.com \
--cc=jgg@ziepe.ca \
--cc=kaishen@linux.alibaba.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox