From: Jakub Kicinski <kuba@kernel.org>
To: Lukasz Majewski <lukma@denx.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
netdev@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
syzbot+3d602af7549af539274e@syzkaller.appspotmail.com
Subject: Re: [PATCH net 1/2] net: hsr: Use the seqnr lock for frames received via interlink port.
Date: Tue, 10 Sep 2024 16:25:17 -0700 [thread overview]
Message-ID: <20240910162517.2b226a71@kernel.org> (raw)
In-Reply-To: <20240909114948.129735b9@wsk>
On Mon, 9 Sep 2024 11:49:48 +0200 Lukasz Majewski wrote:
> > + if (port->type == HSR_PT_INTERLINK) {
> > + spin_lock_bh(&hsr->seqnr_lock);
>
> I'm just wondering if this could have impact on offloaded HSR operation.
>
> I will try to run hsr_redbox.sh test on this patch (with QEMU) and
> share results.
Hi Lukasz, any luck with the testing?
next prev parent reply other threads:[~2024-09-10 23:25 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 [this message]
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
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=20240910162517.2b226a71@kernel.org \
--to=kuba@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=lukma@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+3d602af7549af539274e@syzkaller.appspotmail.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 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).