public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexandra Winter <wintera@linux.ibm.com>
To: Wen Gu <guwen@linux.alibaba.com>,
	wenjia@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, kgraul@linux.ibm.com,
	jaka@linux.ibm.com
Cc: borntraeger@linux.ibm.com, svens@linux.ibm.com,
	alibuda@linux.alibaba.com, tonylu@linux.alibaba.com,
	raspl@linux.ibm.com, schnelle@linux.ibm.com,
	linux-s390@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 7/7] net/smc: manage system EID in SMC stack instead of ISM driver
Date: Mon, 27 Nov 2023 15:04:05 +0100	[thread overview]
Message-ID: <48732f15-64bf-4bb7-8b88-95263a99cf6a@linux.ibm.com> (raw)
In-Reply-To: <1700836935-23819-8-git-send-email-guwen@linux.alibaba.com>



On 24.11.23 15:42, Wen Gu wrote:
> The System EID (SEID) is an internal EID that is used by the SMCv2
> software stack that has a predefined and constant value representing
> the s390 physical machine that the OS is executing on. So it should
> be managed by SMC stack instead of ISM driver and be consistent for
> all ISMv2 device (including virtual ISM devices) on s390 architecture.
> 
> Suggested-by: Alexandra Winter <wintera@linux.ibm.com>
> Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
> ---

Yes, this is what I had in mind. Thank you Wen Gu.
[...]

> 
> diff --git a/drivers/s390/net/ism.h b/drivers/s390/net/ism.h
> index 70c5bbd..49ccbd68 100644
> --- a/drivers/s390/net/ism.h
> +++ b/drivers/s390/net/ism.h

Please remove ISM_IDENT_MASK from drivers/s390/net/ism.h
[...]

> --- a/drivers/s390/net/ism_drv.c
> +++ b/drivers/s390/net/ism_drv.c
> @@ -36,6 +36,7 @@
[...]
> -static void ism_create_system_eid(void)
> -{
> -	struct cpuid id;
> -	u16 ident_tail;
> -	char tmp[5];
> -
> -	get_cpu_id(&id);
> -	ident_tail = (u16)(id.ident & ISM_IDENT_MASK);
> -	snprintf(tmp, 5, "%04X", ident_tail);
> -	memcpy(&SYSTEM_EID.serial_number, tmp, 4);
> -	snprintf(tmp, 5, "%04X", id.machine);
> -	memcpy(&SYSTEM_EID.type, tmp, 4);
> -}
> -
[...]
> @@ -560,7 +535,7 @@ static int ism_dev_init(struct ism_dev *ism)
>  
>  	if (!ism_add_vlan_id(ism, ISM_RESERVED_VLANID))
>  		/* hardware is V2 capable */
> -		ism_create_system_eid();
> +		ism_v2_capable = true;
>  

Please assign 'false' in the else path.
This is required here for backwards compatibility. Hardware that only supports v1,
will reject ISM_RESERVED_VLANID.

[...]


> --- a/net/smc/smc_ism.c
> +++ b/net/smc/smc_ism.c
[...]
> @@ -70,6 +91,11 @@ bool smc_ism_is_v2_capable(void)
>  	return smc_ism_v2_capable;
>  }
>  
> +void smc_ism_set_v2_capable(void)
> +{
> +	smc_ism_v2_capable = true;
> +}
> +
>  /* Set a connection using this DMBE. */
>  void smc_ism_set_conn(struct smc_connection *conn)
>  {
> @@ -431,14 +457,8 @@ static void smcd_register_dev(struct ism_dev *ism)
>  
>  	mutex_lock(&smcd_dev_list.mutex);
>  	if (list_empty(&smcd_dev_list.list)) {
> -		u8 *system_eid = NULL;
> -
> -		system_eid = smcd->ops->get_system_eid();
> -		if (smcd->ops->supports_v2()) {
> -			smc_ism_v2_capable = true;
> -			memcpy(smc_ism_v2_system_eid, system_eid,
> -			       SMC_MAX_EID_LEN);
> -		}
> +		if (smcd->ops->supports_v2())
> +			smc_ism_set_v2_capable();

I don't see the benefit in declaring smc_ism_set_v2_capable() and exporting it in smc_ism.h,
when it is used only once and only here. 
Why don't you just set 
	smc_ism_v2_capable = true;
here?

[...]
> diff --git a/net/smc/smc_ism.h b/net/smc/smc_ism.h
> index 0e5e563..6903cd5 100644
> --- a/net/smc/smc_ism.h
> +++ b/net/smc/smc_ism.h
> @@ -16,6 +16,7 @@
>  #include "smc.h"
>  
>  #define SMC_VIRTUAL_ISM_CHID_MASK	0xFF00
> +#define SMC_ISM_IDENT_MASK		0x00FFFF
>  
[...]
> @@ -45,6 +52,7 @@ int smc_ism_register_dmb(struct smc_link_group *lgr, int buf_size,
>  void smc_ism_get_system_eid(u8 **eid);
>  u16 smc_ism_get_chid(struct smcd_dev *dev);
>  bool smc_ism_is_v2_capable(void);
> +void smc_ism_set_v2_capable(void);
>  int smc_ism_init(void);
>  void smc_ism_exit(void);
>  int smcd_nl_get_device(struct sk_buff *skb, struct netlink_callback *cb);

  reply	other threads:[~2023-11-27 14:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24 14:42 [PATCH net-next v2 0/7] net/smc: implement SMCv2.1 virtual ISM device support Wen Gu
2023-11-24 14:42 ` [PATCH net-next v2 1/7] net/smc: Rename some variable 'fce' to 'fce_v2x' for clarity Wen Gu
2023-11-29 12:50   ` Wenjia Zhang
2023-11-30 11:02     ` Wen Gu
2023-11-24 14:42 ` [PATCH net-next v2 2/7] net/smc: support SMCv2.x supplemental features negotiation Wen Gu
2023-11-24 14:42 ` [PATCH net-next v2 3/7] net/smc: introduce virtual ISM device support feature Wen Gu
2023-11-24 14:42 ` [PATCH net-next v2 4/7] net/smc: define a reserved CHID range for virtual ISM devices Wen Gu
2023-11-24 14:42 ` [PATCH net-next v2 5/7] net/smc: compatible with 128-bits extend GID of virtual ISM device Wen Gu
2023-11-24 14:42 ` [PATCH net-next v2 6/7] net/smc: disable SEID on non-s390 archs where virtual ISM may be used Wen Gu
2023-11-24 14:42 ` [PATCH net-next v2 7/7] net/smc: manage system EID in SMC stack instead of ISM driver Wen Gu
2023-11-27 14:04   ` Alexandra Winter [this message]
2023-11-28  3:13     ` Wen Gu
2023-11-29 12:50 ` [PATCH net-next v2 0/7] net/smc: implement SMCv2.1 virtual ISM device support Wenjia Zhang

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=48732f15-64bf-4bb7-8b88-95263a99cf6a@linux.ibm.com \
    --to=wintera@linux.ibm.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=guwen@linux.alibaba.com \
    --cc=hca@linux.ibm.com \
    --cc=jaka@linux.ibm.com \
    --cc=kgraul@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=raspl@linux.ibm.com \
    --cc=schnelle@linux.ibm.com \
    --cc=svens@linux.ibm.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