From: Guangguan Wang <guangguan.wang@linux.alibaba.com>
To: wenjia@linux.ibm.com, jaka@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,
horms@kernel.org
Cc: linux-rdma@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH net-next v3 0/2] net/smc: Two features for smc-r
Date: Mon, 9 Dec 2024 21:06:47 +0800 [thread overview]
Message-ID: <20241209130649.34591-1-guangguan.wang@linux.alibaba.com> (raw)
v2 -> v3:
(https://lore.kernel.org/netdev/20241202125203.48821-1-guangguan.wang@linux.alibaba.com/)
Patch #1 add 'Reviewed-by' tag.
Patch #2 remove the condition when IPV6 is disabled, and change the
condition to an easier understanding way. Correct the typo and add
'Reviewed-by' tag.
v1 -> v2:
Patch #2 fix build error reported by kernel test robot <lkp@intel.com>.
https://lore.kernel.org/oe-kbuild-all/202411282154.DjX7ilwF-lkp@intel.com/
Guangguan Wang (2):
net/smc: support SMC-R V2 for rdma devices with max_recv_sge equals to
1
net/smc: support ipv4 mapped ipv6 addr client for smc-r v2
net/smc/af_smc.c | 5 ++++-
net/smc/smc_core.c | 5 +++++
net/smc/smc_core.h | 11 ++++++++++-
net/smc/smc_ib.c | 3 +--
net/smc/smc_llc.c | 21 +++++++++++++++------
net/smc/smc_wr.c | 42 +++++++++++++++++++++---------------------
6 files changed, 56 insertions(+), 31 deletions(-)
--
2.24.3 (Apple Git-128)
next reply other threads:[~2024-12-09 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 13:06 Guangguan Wang [this message]
2024-12-09 13:06 ` [PATCH net-next v3 1/2] net/smc: support SMC-R V2 for rdma devices with max_recv_sge equals to 1 Guangguan Wang
2024-12-09 13:06 ` [PATCH net-next v3 2/2] net/smc: support ipv4 mapped ipv6 addr client for smc-r v2 Guangguan Wang
2024-12-09 14:10 ` Wenjia Zhang
2024-12-09 23:43 ` Jakub Kicinski
2024-12-10 12:50 ` Wenjia Zhang
2024-12-10 10:57 ` Guangguan Wang
2024-12-10 11:10 ` Halil Pasic
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=20241209130649.34591-1-guangguan.wang@linux.alibaba.com \
--to=guangguan.wang@linux.alibaba.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=guwen@linux.alibaba.com \
--cc=horms@kernel.org \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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