From: Wen Gu <guwen@linux.alibaba.com>
To: Alexandra Winter <wintera@linux.ibm.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,
guangguan.wang@linux.alibaba.com, linux-s390@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v5 2/9] net/smc: introduce sub-functions for smc_clc_send_confirm_accept()
Date: Mon, 11 Dec 2023 18:57:13 +0800 [thread overview]
Message-ID: <64e8d13a-5811-774b-9e94-20ff747b1d0d@linux.alibaba.com> (raw)
In-Reply-To: <3b3b5b33-1088-47c3-8cbc-4079c6ff472e@linux.ibm.com>
On 2023/12/11 17:47, Alexandra Winter wrote:
>
>
> On 09.12.23 03:50, Wen Gu wrote:
>>
>>
>> On 2023/12/8 15:40, Wen Gu wrote:
>>
>>> There is a large if-else block in smc_clc_send_confirm_accept() and it
>>> is better to split it into two sub-functions.
>>>
>>> Suggested-by: Alexandra Winter <wintera@linux.ibm.com>
>>> Signed-off-by: Wen Gu <guwen@linux.alibaba.com>
>>> ---
>>> net/smc/smc_clc.c | 196 +++++++++++++++++++++++++++++++-----------------------
>>> 1 file changed, 114 insertions(+), 82 deletions(-)
>>>
>>> diff --git a/net/smc/smc_clc.c b/net/smc/smc_clc.c
>>> index 0fcb035..52b4ea9 100644
>>> --- a/net/smc/smc_clc.c
>>> +++ b/net/smc/smc_clc.c
>>> @@ -998,6 +998,111 @@ int smc_clc_send_proposal(struct smc_sock *smc, struct smc_init_info *ini)
>>> return reason_code;
>>> }
>>> +static void smcd_clc_prep_confirm_accept(struct smc_connection *conn,
>>> + struct smc_clc_msg_accept_confirm_v2 *clc_v2,
>>
>> checkpatch will complain 'Alignment should match open parenthesis' here.
>> But in order to make the length less than 80 columns, there seems to be
>> no other good way.
>>
>>> + int first_contact, u8 version,
>>> + u8 *eid, struct smc_init_info *ini,
>>> + int *fce_len,
>>> + struct smc_clc_first_contact_ext_v2x *fce_v2x,
>>> + struct smc_clc_msg_trail *trl)
>>> +{
>> <...>
>>
>>> +
>>> +static void smcr_clc_prep_confirm_accept(struct smc_connection *conn,
>>> + struct smc_clc_msg_accept_confirm_v2 *clc_v2,
>>
>> And here.
>>
>>> + int first_contact, u8 version,
>>> + u8 *eid, struct smc_init_info *ini,
>>> + int *fce_len,
>>> + struct smc_clc_first_contact_ext_v2x *fce_v2x,
>>> + struct smc_clc_fce_gid_ext *gle,
>>> + struct smc_clc_msg_trail *trl)
>>> +{
>> <...>
>>
>
>
> You could shorten the names of the functions
Thank you. I thought about that too, but I think shortening the name may
have an impact on the understanding.
I think the following may be another way out and checkpatch is happy:
+static void
+smcd_clc_prep_confirm_accept(struct smc_connection *conn,
+ struct smc_clc_msg_accept_confirm_v2 *clc_v2,
+ int first_contact, u8 version,
+ u8 *eid, struct smc_init_info *ini,
+ int *fce_len,
+ struct smc_clc_first_contact_ext_v2x *fce_v2x,
+ struct smc_clc_msg_trail *trl)
and
+static void
+smcr_clc_prep_confirm_accept(struct smc_connection *conn,
+ struct smc_clc_msg_accept_confirm_v2 *clc_v2,
+ int first_contact, u8 version,
+ u8 *eid, struct smc_init_info *ini,
+ int *fce_len,
+ struct smc_clc_first_contact_ext_v2x *fce_v2x,
+ struct smc_clc_fce_gid_ext *gle,
+ struct smc_clc_msg_trail *trl)
next prev parent reply other threads:[~2023-12-11 10:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 7:40 [PATCH net-next v5 0/9] net/smc: implement SMCv2.1 virtual ISM device support Wen Gu
2023-12-08 7:40 ` [PATCH net-next v5 1/9] net/smc: rename some 'fce' to 'fce_v2x' for clarity Wen Gu
2023-12-08 7:40 ` [PATCH net-next v5 2/9] net/smc: introduce sub-functions for smc_clc_send_confirm_accept() Wen Gu
2023-12-09 2:50 ` Wen Gu
2023-12-11 9:47 ` Alexandra Winter
2023-12-11 10:57 ` Wen Gu [this message]
2023-12-11 10:43 ` Alexandra Winter
2023-12-11 12:15 ` Wen Gu
2023-12-11 13:35 ` Alexandra Winter
2023-12-11 15:23 ` Wen Gu
2023-12-08 7:40 ` [PATCH net-next v5 3/9] net/smc: support SMCv2.x supplemental features negotiation Wen Gu
2023-12-08 7:40 ` [PATCH net-next v5 4/9] net/smc: introduce virtual ISM device support feature Wen Gu
2023-12-08 7:40 ` [PATCH net-next v5 5/9] net/smc: define a reserved CHID range for virtual ISM devices Wen Gu
2023-12-11 8:24 ` Alexandra Winter
2023-12-11 8:41 ` Wen Gu
2023-12-08 7:40 ` [PATCH net-next v5 6/9] net/smc: compatible with 128-bits extended GID of virtual ISM device Wen Gu
2023-12-11 11:37 ` Alexandra Winter
2023-12-08 7:40 ` [PATCH net-next v5 7/9] net/smc: support extended GID in SMC-D lgr netlink attribute Wen Gu
2023-12-11 9:39 ` Alexandra Winter
2023-12-11 10:09 ` Wen Gu
2023-12-11 11:50 ` Alexandra Winter
2023-12-08 7:40 ` [PATCH net-next v5 8/9] net/smc: disable SEID on non-s390 archs where virtual ISM may be used Wen Gu
2023-12-08 7:40 ` [PATCH net-next v5 9/9] net/smc: manage system EID in SMC stack instead of ISM driver Wen Gu
2023-12-11 8:29 ` Alexandra Winter
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=64e8d13a-5811-774b-9e94-20ff747b1d0d@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=guangguan.wang@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 \
--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