From: Ido Schimmel <idosch@nvidia.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: kuba@kernel.org, Duanqiang Wen <duanqiangwen@net-swift.com>,
netdev@vger.kernel.org, mengyuanlou@net-swift.com,
davem@davemloft.net, edumazet@google.com,
maciej.fijalkowski@intel.com, andrew@lunn.ch,
wangxiongfeng2@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: txgbe: fix clk_name exceed MAX_DEV_ID limits
Date: Mon, 18 Mar 2024 19:29:32 +0200 [thread overview]
Message-ID: <Zfh5_CpMJC8KU_yG@shredder> (raw)
In-Reply-To: <24a7051fdcd1f156c3704bca39e4b3c41dfc7c4b.camel@redhat.com>
On Thu, Mar 14, 2024 at 01:46:01PM +0100, Paolo Abeni wrote:
> Unrelated to this patch, but more related to the self-test burst this
> patch landed into: it looks like that since roughly the net-next PR was
> merged back forwarding debug variant of the vxlan-bridge-1q-ipv6-sh and
> vxlan-bridge-1d-port-8472-ipv6-sh tests become less stable.
>
> IDK if that was due to some glitch in the AWS hosts or what else. Just
> an head-up.
Looked into it. The test is sending 100 pings with an interval of 0.1
seconds and using a timeout of 11 seconds which is borderline,
especially with a debug kernel. Will bump it to 20 seconds for good
measures. It won't prolong the test unless something is actually wrong,
in which case the test will rightfully fail.
next prev parent reply other threads:[~2024-03-18 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 8:06 [PATCH] net: txgbe: fix clk_name exceed MAX_DEV_ID limits Duanqiang Wen
2024-03-13 10:43 ` Michal Kubiak
2024-03-14 12:46 ` Paolo Abeni
2024-03-18 17:29 ` Ido Schimmel [this message]
2024-03-14 13:00 ` 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=Zfh5_CpMJC8KU_yG@shredder \
--to=idosch@nvidia.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=duanqiangwen@net-swift.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=mengyuanlou@net-swift.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=wangxiongfeng2@huawei.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).