From: Wen Gu <guwen@linux.alibaba.com>
To: Jan Karcher <jaka@linux.ibm.com>,
wintera@linux.ibm.com, twinkler@linux.ibm.com, hca@linux.ibm.com,
gor@linux.ibm.com, agordeev@linux.ibm.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
wenjia@linux.ibm.com
Cc: borntraeger@linux.ibm.com, svens@linux.ibm.com,
alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next v4 03/11] net/smc: implement ID-related operations of loopback-ism
Date: Fri, 22 Mar 2024 09:37:32 +0800 [thread overview]
Message-ID: <8bf123c3-4835-46c5-ada3-6d94fab34e65@linux.alibaba.com> (raw)
In-Reply-To: <468c16e7-b546-4017-8876-358b87f70f84@linux.ibm.com>
On 2024/3/21 16:12, Jan Karcher wrote:
>
>
> On 17/03/2024 11:05, Wen Gu wrote:
>> This implements GID and CHID related operations of loopback-ism device.
>> loopback-ism acts as an ISMv2. It's GID is generated randomly by UUIDv4
>> algorithm and CHID is reserved 0xFFFF.
>
> Hi Wen Gu,
>
> Please add that loopback-ism uses an extended GID instead of a GID here aswell.
>
OK, will add that. Thanks!
>>
>> Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
>> ---
>> net/smc/smc_loopback.c | 62 ++++++++++++++++++++++++++++++++++++++----
>> net/smc/smc_loopback.h | 3 ++
>> 2 files changed, 60 insertions(+), 5 deletions(-)
>>
>> diff --git a/net/smc/smc_loopback.c b/net/smc/smc_loopback.c
>> index e9170d86e58f..7656a2474500 100644
>> --- a/net/smc/smc_loopback.c
>> +++ b/net/smc/smc_loopback.c
>> @@ -19,11 +19,62 @@
>> #include "smc_loopback.h"
>> #if IS_ENABLED(CONFIG_SMC_LO)
>> +#define SMC_LO_V2_CAPABLE 0x1 /* loopback-ism acts as ISMv2 */
>> +
>> static const char smc_lo_dev_name[] = "loopback-ism";
>> static struct smc_lo_dev *lo_dev;
>> +static void smc_lo_generate_id(struct smc_lo_dev *ldev)
>> +{
>> + struct smcd_gid *lgid = &ldev->local_gid;
>> + uuid_t uuid;
>> +
>> + uuid_gen(&uuid);
>> + memcpy(&lgid->gid, &uuid, sizeof(lgid->gid));
>> + memcpy(&lgid->gid_ext, (u8 *)&uuid + sizeof(lgid->gid),
>> + sizeof(lgid->gid_ext));
>> +
>> + ldev->chid = SMC_LO_CHID;
>> +}
>
> Minor comment. The function name implies that there is one id set whle
> there are two different ones. The chid assignment can be easily looked over. Maybe changing the function name to
> `smc_lo_generate_ids` would prevent this. What do you think?
>
Agree. I will change the function name to 'smc_lo_generate_ids'. Thanks!
> Thanks
> - Jan
>
>> +
>> +static int smc_lo_query_rgid(struct smcd_dev *smcd, struct smcd_gid *rgid,
>> + u32 vid_valid, u32 vid)
>> +{
>> + struct smc_lo_dev *ldev = smcd->priv;
>> +
>> + /* rgid should be the same as lgid */
>> + if (!ldev || rgid->gid != ldev->local_gid.gid ||
>> + rgid->gid_ext != ldev->local_gid.gid_ext)
>> + return -ENETUNREACH;
>> + return 0;
>> +}
>> +
>> +static int smc_lo_supports_v2(void)
>> +{
>> + return SMC_LO_V2_CAPABLE;
>> +}
>> +
>> +static void smc_lo_get_local_gid(struct smcd_dev *smcd,
>> + struct smcd_gid *smcd_gid)
>> +{
>> + struct smc_lo_dev *ldev = smcd->priv;
>> +
>> + smcd_gid->gid = ldev->local_gid.gid;
>> + smcd_gid->gid_ext = ldev->local_gid.gid_ext;
>> +}
>> +
>> +static u16 smc_lo_get_chid(struct smcd_dev *smcd)
>> +{
>> + return ((struct smc_lo_dev *)smcd->priv)->chid;
>> +}
>> +
>> +static struct device *smc_lo_get_dev(struct smcd_dev *smcd)
>> +{
>> + return &((struct smc_lo_dev *)smcd->priv)->dev;
>> +}
>> +
>> static const struct smcd_ops lo_ops = {
>> - .query_remote_gid = NULL,
>> + .query_remote_gid = smc_lo_query_rgid,
>> .register_dmb = NULL,
>> .unregister_dmb = NULL,
>> .add_vlan_id = NULL,
>> @@ -32,10 +83,10 @@ static const struct smcd_ops lo_ops = {
>> .reset_vlan_required = NULL,
>> .signal_event = NULL,
>> .move_data = NULL,
>> - .supports_v2 = NULL,
>> - .get_local_gid = NULL,
>> - .get_chid = NULL,
>> - .get_dev = NULL,
>> + .supports_v2 = smc_lo_supports_v2,
>> + .get_local_gid = smc_lo_get_local_gid,
>> + .get_chid = smc_lo_get_chid,
>> + .get_dev = smc_lo_get_dev,
>> };
>> static struct smcd_dev *smcd_lo_alloc_dev(const struct smcd_ops *ops,
>> @@ -95,6 +146,7 @@ static void smcd_lo_unregister_dev(struct smc_lo_dev *ldev)
>> static int smc_lo_dev_init(struct smc_lo_dev *ldev)
>> {
>> + smc_lo_generate_id(ldev);
>> return smcd_lo_register_dev(ldev);
>> }
>> diff --git a/net/smc/smc_loopback.h b/net/smc/smc_loopback.h
>> index 9dd44d4c0ca3..55b41133a97f 100644
>> --- a/net/smc/smc_loopback.h
>> +++ b/net/smc/smc_loopback.h
>> @@ -20,10 +20,13 @@
>> #if IS_ENABLED(CONFIG_SMC_LO)
>> #define SMC_LO_MAX_DMBS 5000
>> +#define SMC_LO_CHID 0xFFFF
>> struct smc_lo_dev {
>> struct smcd_dev *smcd;
>> struct device dev;
>> + u16 chid;
>> + struct smcd_gid local_gid;
>> };
>> #endif
next prev parent reply other threads:[~2024-03-22 1:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 10:05 [RFC PATCH net-next v4 00/11] net/smc: SMC intra-OS shortcut with loopback-ism Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 01/11] net/smc: decouple ism_client from SMC-D DMB registration Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 02/11] net/smc: introduce loopback-ism for SMC intra-OS shortcut Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 03/11] net/smc: implement ID-related operations of loopback-ism Wen Gu
2024-03-21 8:12 ` Jan Karcher
2024-03-22 1:37 ` Wen Gu [this message]
2024-03-17 10:05 ` [RFC PATCH net-next v4 04/11] net/smc: implement some unsupported " Wen Gu
2024-03-21 8:12 ` Jan Karcher
2024-03-22 1:39 ` Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 05/11] net/smc: implement DMB-related " Wen Gu
2024-03-21 8:12 ` Jan Karcher
2024-03-22 12:30 ` Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 06/11] net/smc: ignore loopback-ism when dumping SMC-D devices Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 07/11] net/smc: register loopback-ism into SMC-D device list Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 08/11] net/smc: add operations to merge sndbuf with peer DMB Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 09/11] net/smc: attach or detach ghost sndbuf to " Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 10/11] net/smc: adapt cursor update when sndbuf and peer DMB are merged Wen Gu
2024-03-21 8:12 ` Jan Karcher
2024-03-22 1:49 ` Wen Gu
2024-03-17 10:05 ` [RFC PATCH net-next v4 11/11] net/smc: implement DMB-merged operations of loopback-ism Wen Gu
2024-03-21 8:11 ` [RFC PATCH net-next v4 00/11] net/smc: SMC intra-OS shortcut with loopback-ism Jan Karcher
2024-03-22 12:36 ` Wen Gu
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=8bf123c3-4835-46c5-ada3-6d94fab34e65@linux.alibaba.com \
--to=guwen@linux.alibaba.com \
--cc=agordeev@linux.ibm.com \
--cc=alibuda@linux.alibaba.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jaka@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=svens@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=twinkler@linux.ibm.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@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