From: Lukasz Majewski <lukma@denx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: netdev@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 2/2] net: hsr: Remove interlink_sequence_nr.
Date: Mon, 9 Sep 2024 11:43:49 +0200 [thread overview]
Message-ID: <20240909114349.229b42b0@wsk> (raw)
In-Reply-To: <20240906132816.657485-3-bigeasy@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]
Hi Sebastian Andrzej,
> From: Eric Dumazet <edumazet@google.com>
>
> Remove interlink_sequence_nr which is unused.
>
> [ bigeasy: split out from Eric's patch ].
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> net/hsr/hsr_device.c | 1 -
> net/hsr/hsr_main.h | 1 -
> 2 files changed, 2 deletions(-)
>
> diff --git a/net/hsr/hsr_device.c b/net/hsr/hsr_device.c
> index a06e790042e2e..10393836992df 100644
> --- a/net/hsr/hsr_device.c
> +++ b/net/hsr/hsr_device.c
> @@ -625,7 +625,6 @@ int hsr_dev_finalize(struct net_device *hsr_dev,
> struct net_device *slave[2], /* Overflow soon to find bugs easier: */
> hsr->sequence_nr = HSR_SEQNR_START;
> hsr->sup_sequence_nr = HSR_SUP_SEQNR_START;
> - hsr->interlink_sequence_nr = HSR_SEQNR_START;
>
> timer_setup(&hsr->announce_timer, hsr_announce, 0);
> timer_setup(&hsr->prune_timer, hsr_prune_nodes, 0);
> diff --git a/net/hsr/hsr_main.h b/net/hsr/hsr_main.h
> index ab1f8d35d9dcf..fcfeb79bb0401 100644
> --- a/net/hsr/hsr_main.h
> +++ b/net/hsr/hsr_main.h
> @@ -203,7 +203,6 @@ struct hsr_priv {
> struct timer_list prune_proxy_timer;
> int announce_count;
> u16 sequence_nr;
> - u16 interlink_sequence_nr; /* Interlink port seq_nr */
I think that this was an attempt to exactly follow standard (point
5.2.2.2 HSR-SAN RedBox for attachment to a single-thread LAN) which
states that proxy node table shall keep for each interlink the sequence
number [*]. Instead in code the sequence number for a new frame which
comes from interlink port is assigned int:
hsr_get_node() -> file line 271
and then this starting sequence numer is used for this proxy node table
node.
Hence it shall be safe to remove it.
> u16 sup_sequence_nr; /* For HSRv1 separate seq_nr for
> supervision */ enum hsr_version prot_version; /* Indicate if
> HSRv0, HSRv1 or PRPv1 */ spinlock_t seqnr_lock; /* locking for
> sequence_nr */
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-09-09 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 13:25 [PATCH net 0/2] net: hsr: Use the seqnr lock for frames received via interlink port Sebastian Andrzej Siewior
2024-09-06 13:25 ` [PATCH net 1/2] " Sebastian Andrzej Siewior
2024-09-09 9:49 ` Lukasz Majewski
2024-09-10 23:25 ` Jakub Kicinski
2024-09-11 7:54 ` Lukasz Majewski
2024-09-11 15:46 ` Lukasz Majewski
2024-09-06 13:25 ` [PATCH net-next 2/2] net: hsr: Remove interlink_sequence_nr Sebastian Andrzej Siewior
2024-09-09 9:43 ` Lukasz Majewski [this message]
2024-09-11 22:53 ` [PATCH net 0/2] net: hsr: Use the seqnr lock for frames received via interlink port Jakub Kicinski
2024-09-12 6:51 ` Sebastian Andrzej Siewior
2024-09-13 0:14 ` Jakub Kicinski
2024-09-13 6:43 ` Sebastian Andrzej Siewior
2024-09-11 23:20 ` patchwork-bot+netdevbpf
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=20240909114349.229b42b0@wsk \
--to=lukma@denx.de \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.