From: Andrew Lunn <andrew@lunn.ch>
To: Javen <javen_xu@realsil.com.cn>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
"andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: r8169: Discussion on implementing RSS support for r8169
Date: Thu, 19 Mar 2026 18:19:36 +0100 [thread overview]
Message-ID: <bb17044d-9dff-4c81-a001-d754c42e0040@lunn.ch> (raw)
In-Reply-To: <1ce3478d571f4d26a45e792c4c84c429@realsil.com.cn>
On Thu, Mar 19, 2026 at 08:56:58AM +0000, Javen wrote:
> Hi, Heiner
>
> We are now planning to implement RSS support on r8169 driver. This will require significant changes to the existing driver architecture, so we want to discuss it with you.
>
> Based on our vendor driver which can be fetched from Realtek, the key modifications will include:
>
> 1. Enable msix and updating the irq allocation mechanism
> 2. Support multiple rx/tx queues
> 3. Register multiple napi and update new interrupt mapping(isr/imr) for multi-queue
> 4. Implement rx msix poll and rx interrupt function
> 5. Implement ethtool callbacks for rss configuration
>
> Should we submit the changes above separately or submit them all at once? Or do you have any other suggestions?
You generally want lots of small patches, each with a good commit
message, which are obviously correct. Given the limit of 15 patches in
one series, you probably need to break it up into a number of series.
Also, having small patches makes git bisect more useful when you
break stuff.
Andrew
next prev parent reply other threads:[~2026-03-19 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-19 8:56 r8169: Discussion on implementing RSS support for r8169 Javen
2026-03-19 17:19 ` Andrew Lunn [this message]
2026-03-19 19:59 ` Heiner Kallweit
2026-03-20 3:22 ` Javen
2026-03-20 7:01 ` Heiner Kallweit
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=bb17044d-9dff-4c81-a001-d754c42e0040@lunn.ch \
--to=andrew@lunn.ch \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=javen_xu@realsil.com.cn \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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