From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Oddbjørn Kvalsund" <oddbjorn.kvalsund@gmail.com>
Cc: netdev@vger.kernel.org, Mika Westerberg <westeri@kernel.org>
Subject: Re: thunderbolt_net performance and receive-side-scaling (RSS)
Date: Thu, 5 Mar 2026 10:06:14 +0100 [thread overview]
Message-ID: <20260305090614.GZ2275908@black.igk.intel.com> (raw)
In-Reply-To: <CAOhm4wpO9gB03qt0kPdEiZtKLD_UOuYx=VbQVWwyXmqS_0_ySA@mail.gmail.com>
Hi,
On Thu, Mar 05, 2026 at 09:56:26AM +0100, Oddbjørn Kvalsund wrote:
> Hi,
>
> I am seeing fairly good network performance between a 2018 Dell XPS15 laptop
> and a 2021 MacBook using Thunderbolt and the thunderbolt_net driver, with jumbo
> frames enabled on both machines (iperf3 results below). However, while iperf3
> is running, one core on the XPS15 is at 100% utilization due to the ksoftirqd
> process. This makes me wonder whether additional performance could be achieved
> if the load were distributed across multiple cores.
>
> From what I can tell, this might relate to receive-side scaling (RSS), which
> does not appear to be implemented in the thunderbolt_net driver. Would adding
> RSS support be worthwhile, or are there architectural limitations that would
> make such an optimization ineffective?
I'm not familiar with that but feel free to experiment and if you find that
it provides better throughput please provide patches :)
USB4NET spec can be downloaded from USB-IF, it's part of USB4 spec.
parent reply other threads:[~2026-03-05 9:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAOhm4wpO9gB03qt0kPdEiZtKLD_UOuYx=VbQVWwyXmqS_0_ySA@mail.gmail.com>]
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=20260305090614.GZ2275908@black.igk.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=oddbjorn.kvalsund@gmail.com \
--cc=westeri@kernel.org \
/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