From: Dust Li <dust.li@linux.alibaba.com>
To: Jan Karcher <jaka@linux.ibm.com>, Liu Jian <liujian56@huawei.com>,
linux-rdma@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org
Cc: jgg@ziepe.ca, leon@kernel.org, zyjzyj2000@gmail.com,
wenjia@linux.ibm.com, alibuda@linux.alibaba.com,
tonylu@linux.alibaba.com, guwen@linux.alibaba.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: [PATCH net-next 0/4] Make SMC-R can work with rxe devices
Date: Wed, 21 Aug 2024 09:03:24 +0800 [thread overview]
Message-ID: <20240821010324.GK103152@linux.alibaba.com> (raw)
In-Reply-To: <0d5e2cec-dd0b-4920-99ff-9299e4df604f@linux.ibm.com>
On 2024-08-20 15:16:57, Jan Karcher wrote:
>
>
>On 09/08/2024 10:31, Liu Jian wrote:
>> Make SMC-R can work with rxe devices. This allows us to easily test and
>> learn the SMC-R protocol without relying on a physical RoCE NIC.
>
>Hi Liu,
>
>sorry for taking quite some time to answer.
>
>Looking into this i cannot accept this series at the given point of time.
>
>FWIU, RXE is mainly for testing and development and i agree that it would be
>a nice thing to have for SMC-R.
>The problem is that there is no clean layer for different RoCE devices
>currently. Adding RXE to it works but isn't clean.
Hi jan,
>Also we have no way to do a "test" build which would have such a device
>supported and a "prod" build which would not support it.
I don't quite understand what you mean here, Maybe I missed something ?
IIUC, we can control whether to use RXE by simpling insmod or rmmod rdma_rxe.ko
I believe having RXE support is beneficial for testing, especially in
simple physical networking setups where many corner cases are unlikely
to occur. By using RXE, we can easily configure unusual scenarios with
the existing iptables/netfilter infrastructure to simulate real-world
situations, such as packet dropping or network retransmission. This
approach can be advantageous for finding hidden bugs.
Best regards,
Dust
>
>Please give us time to investigate how to solve this in a neat way without
>building up to much technical debt.
>
>Thanks for your contribution and making us aware of this area of improvment.
>- Jan
>
>>
>> Liu Jian (4):
>> rdma/device: export ib_device_get_netdev()
>> net/smc: use ib_device_get_netdev() helper to get netdev info
>> net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync()
>> RDMA/rxe: Set queue pair cur_qp_state when being queried
>>
>> drivers/infiniband/core/core_priv.h | 3 ---
>> drivers/infiniband/core/device.c | 1 +
>> drivers/infiniband/sw/rxe/rxe_verbs.c | 2 ++
>> include/rdma/ib_verbs.h | 2 ++
>> net/smc/smc_ib.c | 10 +++++-----
>> net/smc/smc_pnet.c | 6 +-----
>> 6 files changed, 11 insertions(+), 13 deletions(-)
>>
next prev parent reply other threads:[~2024-08-21 1:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 8:31 [PATCH net-next 0/4] Make SMC-R can work with rxe devices Liu Jian
2024-08-09 8:31 ` [PATCH net-next 1/4] rdma/device: export ib_device_get_netdev() Liu Jian
2024-08-09 8:31 ` [PATCH net-next 2/4] net/smc: use ib_device_get_netdev() helper to get netdev info Liu Jian
2024-08-09 14:59 ` Dust Li
2024-08-12 2:07 ` liujian (CE)
2024-08-12 2:43 ` Dust Li
2024-08-09 8:31 ` [PATCH net-next 3/4] net/smc: fix one NULL pointer dereference in smc_ib_is_sg_need_sync() Liu Jian
2024-08-09 10:01 ` Wen Gu
2024-08-09 14:59 ` Dust Li
2024-08-12 3:30 ` D. Wythe
2024-08-09 8:31 ` [PATCH net-next 4/4] RDMA/rxe: Set queue pair cur_qp_state when being queried Liu Jian
2024-08-09 11:06 ` Zhu Yanjun
2024-08-11 8:31 ` Leon Romanovsky
[not found] ` <bb0a5de8-f2d3-4276-ada4-f788f574b798@linux.dev>
2024-08-11 10:24 ` Zhu Yanjun
2024-08-11 6:05 ` [PATCH net-next 0/4] Make SMC-R can work with rxe devices Jan Karcher
2024-08-20 13:16 ` Jan Karcher
2024-08-21 1:03 ` Dust Li [this message]
2024-08-24 10:04 ` liujian (CE)
2024-08-26 19:04 ` Jan Karcher
2024-08-28 10:29 ` liujian (CE)
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=20240821010324.GK103152@linux.alibaba.com \
--to=dust.li@linux.alibaba.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=liujian56@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.com \
--cc=zyjzyj2000@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).