From: Andrew Lunn <andrew@lunn.ch>
To: Hangbin Liu <hangbin.liu@linux.dev>
Cc: Jakub Kicinski <kuba@kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Hangbin Liu <liuhangbin@kylinos.cn>
Subject: Re: [PATCH net-next 1/2] netdevsim: add link speed support
Date: Wed, 2 Sep 2026 14:49:45 +0200 [thread overview]
Message-ID: <a23b1446-d541-4f2d-ab3f-474285b5d7b4@lunn.ch> (raw)
In-Reply-To: <apeDXBASpPvAaWcG@fedora>
On Wed, Sep 02, 2026 at 10:01:00AM +0800, Hangbin Liu wrote:
> On Tue, Sep 01, 2026 at 04:21:04PM +0200, Andrew Lunn wrote:
> > > OK, here is the reason. In taprio_set_picos_per_byte(), it init NIC speed to
> > > SPEED_10. If the NIC doesn't support get_link_ksettings, the final calculated
> > > picos_per_byte would be a extremely large number 800000. The later tc taprio
> > > testing `tc qdisc ... sched-entry S 02 300` will always failed in
> > > fill_sched_entry(), as min_duration is also a large number 48000.
> > >
> > > After we supports get_link_ksettings for netdevsim, the speed is 5000 and
> > > picos_per_byte will be init to 1600. The later min_duration checking in
> > > fill_sched_entry() is 300 vs 96. So the tc qdisc command always return 0.
> > >
> > > To fix the test, I think we should reduce the interval number. e.g.
> >
> > Why not just set the initial speed to SPEED_10, so nothing changes?
> >
>
> `nsim_leaf_tx_share_set` and `nsim_leaf_tx_max_set` compare against
> `NSIM_LINK_SPEED_MAX` for TX‑rate setting. Using `SPEED_10` as the value
> appears too small. I am concerned this could break other existing tests.
Well, 10MBps has been around since 1983. I've not counted, but if you
look at all the devices which Linux supports, i expect it is the most
popular speed.
I suggest you give it a try, and run all the tests. See what
happens. But to me, it is a safe choice.
Andrew
next prev parent reply other threads:[~2026-09-02 12:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 3:28 [PATCH net-next 0/2] netdevsim: add link speed support Hangbin Liu
2026-08-31 3:28 ` [PATCH net-next 1/2] " Hangbin Liu
2026-08-31 12:16 ` Andrew Lunn
2026-09-01 6:39 ` Hangbin Liu
2026-09-01 12:43 ` Andrew Lunn
2026-09-02 1:53 ` Hangbin Liu
2026-09-02 12:38 ` Andrew Lunn
2026-08-31 12:24 ` Andrew Lunn
2026-09-01 6:31 ` Hangbin Liu
2026-08-31 22:08 ` Jakub Kicinski
2026-09-01 6:58 ` Hangbin Liu
2026-09-01 8:23 ` Hangbin Liu
2026-09-01 14:21 ` Andrew Lunn
2026-09-02 2:01 ` Hangbin Liu
2026-09-02 12:49 ` Andrew Lunn [this message]
2026-09-01 14:18 ` Andrew Lunn
2026-08-31 3:28 ` [PATCH net-next 2/2] selftests: netdevsim: add speed testing Hangbin Liu
2026-08-31 22:06 ` Jakub Kicinski
2026-09-01 6:42 ` Hangbin Liu
2026-09-01 15:06 ` Jakub Kicinski
2026-09-02 2:04 ` Hangbin Liu
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=a23b1446-d541-4f2d-ab3f-474285b5d7b4@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hangbin.liu@linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=liuhangbin@kylinos.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=vladimir.oltean@nxp.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