From: Saeed Mahameed <saeed@kernel.org>
To: Karsten Graul <kgraul@linux.ibm.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
hca@linux.ibm.com, raspl@linux.ibm.com
Subject: Re: [PATCH net-next v2 06/15] net/smc: Add diagnostic information to link structure
Date: Tue, 03 Nov 2020 17:06:39 -0800 [thread overview]
Message-ID: <f734400e8fbf53d3c8a4db97887bd55f6f80f10b.camel@kernel.org> (raw)
In-Reply-To: <20201103102531.91710-7-kgraul@linux.ibm.com>
On Tue, 2020-11-03 at 11:25 +0100, Karsten Graul wrote:
> From: Guvenc Gulce <guvenc@linux.ibm.com>
>
> During link creation add network and ib-device name to
> link structure. This is needed for diagnostic purposes.
>
> When diagnostic information is gathered, we need to traverse
> device, linkgroup and link structures, to be able to do that
> we need to hold a spinlock for the linkgroup list, without this
> diagnostic information in link structure, another device list
> mutex holding would be necessary to dereference the device
> pointer in the link structure which would be impossible when
> holding a spinlock already.
>
> Signed-off-by: Guvenc Gulce <guvenc@linux.ibm.com>
> Signed-off-by: Karsten Graul <kgraul@linux.ibm.com>
> ---
> net/smc/smc_core.c | 10 ++++++++++
> net/smc/smc_core.h | 3 +++
> 2 files changed, 13 insertions(+)
>
> diff --git a/net/smc/smc_core.c b/net/smc/smc_core.c
> index da94725deb09..28fc583d9033 100644
> --- a/net/smc/smc_core.c
> +++ b/net/smc/smc_core.c
> @@ -303,6 +303,15 @@ static u8 smcr_next_link_id(struct
> smc_link_group *lgr)
> return link_id;
> }
>
> +static inline void smcr_copy_dev_info_to_link(struct smc_link *link)
> +{
> + struct smc_ib_device *smcibdev = link->smcibdev;
> +
> + memcpy(link->ibname, smcibdev->ibdev->name, sizeof(link-
> >ibname));
> + memcpy(link->ndevname, smcibdev->netdev[link->ibport - 1],
> + sizeof(link->ndevname));
snprintf()
> +}
> +
> int smcr_link_init(struct smc_link_group *lgr, struct smc_link *lnk,
> u8 link_idx, struct smc_init_info *ini)
> {
> @@ -317,6 +326,7 @@ int smcr_link_init(struct smc_link_group *lgr,
> struct smc_link *lnk,
> lnk->smcibdev = ini->ib_dev;
> lnk->ibport = ini->ib_port;
> atomic_inc(&ini->ib_dev->lnk_cnt_by_port[ini->ib_port - 1]);
> + smcr_copy_dev_info_to_link(lnk);
> lnk->path_mtu = ini->ib_dev->pattr[ini->ib_port -
> 1].active_mtu;
> atomic_set(&lnk->conn_cnt, 0);
> smc_llc_link_set_uid(lnk);
> diff --git a/net/smc/smc_core.h b/net/smc/smc_core.h
> index 83a88a4635db..bd16d63c5222 100644
> --- a/net/smc/smc_core.h
> +++ b/net/smc/smc_core.h
> @@ -124,6 +124,9 @@ struct smc_link {
> u8 link_is_asym; /* is link
> asymmetric? */
> struct smc_link_group *lgr; /* parent link group
> */
> struct work_struct link_down_wrk; /* wrk to bring link
> down */
> + /* Diagnostic relevant link information */
> + u8 ibname[IB_DEVICE_NAME_MAX];/* ib
> device name */
> + u8 ndevname[IFNAMSIZ];/* network device
> name */
>
IMHO, Comments are redundant. and you could define name buffers as
char array for more natural string manipulation down the road.
next prev parent reply other threads:[~2020-11-04 1:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 10:25 [PATCH net-next v2 00/15] net/smc: extend diagnostic netlink interface Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 01/15] net/smc: use helper smc_conn_abort() in listen processing Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 02/15] net/smc: Use active link of the connection Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 03/15] net/smc: Add connection counters for links Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 04/15] net/smc: Add link counters for IB device ports Karsten Graul
2020-11-04 0:52 ` Saeed Mahameed
2020-11-03 10:25 ` [PATCH net-next v2 05/15] net/smc: Add diagnostic information to smc ib-device Karsten Graul
2020-11-04 1:00 ` Saeed Mahameed
2020-11-03 10:25 ` [PATCH net-next v2 06/15] net/smc: Add diagnostic information to link structure Karsten Graul
2020-11-04 1:06 ` Saeed Mahameed [this message]
2020-11-03 10:25 ` [PATCH net-next v2 07/15] net/smc: Refactor the netlink reply processing routine Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 08/15] net/smc: Add ability to work with extended SMC netlink API Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 09/15] net/smc: Introduce SMCR get linkgroup command Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 10/15] net/smc: Introduce SMCR get link command Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 11/15] net/smc: Add SMC-D Linkgroup diagnostic support Karsten Graul
2020-11-04 1:26 ` Saeed Mahameed
2020-11-03 10:25 ` [PATCH net-next v2 12/15] net/smc: Add support for obtaining SMCD device list Karsten Graul
2020-11-04 1:31 ` Saeed Mahameed
2020-11-06 6:38 ` Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 13/15] net/smc: Add support for obtaining SMCR " Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 14/15] net/smc: Refactor smc ism v2 capability handling Karsten Graul
2020-11-03 10:25 ` [PATCH net-next v2 15/15] net/smc: Add support for obtaining system information Karsten Graul
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=f734400e8fbf53d3c8a4db97887bd55f6f80f10b.camel@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@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;
as well as URLs for NNTP newsgroup(s).