From: Joe Damato <jdamato@fastly.com>
To: netdev@vger.kernel.org
Cc: Joe Damato <jdamato@fastly.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org (open list),
Michael Chan <mchan@broadcom.com>,
Paolo Abeni <pabeni@redhat.com>,
Pavan Chebbi <pavan.chebbi@broadcom.com>
Subject: [RFC net-next v2 0/2] tg3: Link IRQs, NAPIs, and queues
Date: Wed, 25 Sep 2024 16:20:46 +0000 [thread overview]
Message-ID: <20240925162048.16208-1-jdamato@fastly.com> (raw)
Greetings:
This RFC v2 follows from a PATCH submission which received some feedback
from broadcom on shortening the patch.
Patch 1 is a revised, shortened version of the original I submit a few
weeks ago [1].
Patch 2 is a new patch to link queues to NAPI instances. See the commit
message for more details and sample output.
I am sending them together as I plan to send them a series when net-next
reopens next week unless there is any feedback or changes requested.
I am hoping that broadcom would be able to take a look before then so
that these patches will be ready for official submission next week :)
Thanks,
Joe
[1]: https://lore.kernel.org/netdev/20240912155830.14688-1-jdamato@fastly.com/
rfv2:
- Switched to RFC (net-next is closed).
- Patch 1 incorporated the feedback from Michael Chan in the thread
linked above to reduce the number of lines of code added.
- Added patch 2, which implements a new feature.
Joe Damato (2):
tg3: Link IRQs to NAPI instances
tg3: Link queues to NAPIs
drivers/net/ethernet/broadcom/tg3.c | 31 ++++++++++++++++++++++-------
1 file changed, 24 insertions(+), 7 deletions(-)
--
2.25.1
next reply other threads:[~2024-09-25 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 16:20 Joe Damato [this message]
2024-09-25 16:20 ` [RFC net-next v2 1/2] tg3: Link IRQs to NAPI instances Joe Damato
2024-09-27 3:58 ` Pavan Chebbi
2024-09-25 16:20 ` [RFC net-next v2 2/2] tg3: Link queues to NAPIs Joe Damato
2024-09-26 23:17 ` Joe Damato
2024-09-27 4:03 ` Pavan Chebbi
2024-09-27 16:14 ` Joe Damato
2024-10-02 23:21 ` Joe Damato
2024-10-03 4:26 ` Pavan Chebbi
2024-10-03 19:47 ` Joe Damato
2024-10-04 15:33 ` Pavan Chebbi
2024-10-04 16:39 ` Joe Damato
-- strict thread matches above, loose matches on Subject: below --
2024-10-05 14:57 [RFC net-next v2 0/2] tg3: Link IRQs, NAPIs, and queues Joe Damato
2024-10-06 21:15 ` Joe Damato
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=20240925162048.16208-1-jdamato@fastly.com \
--to=jdamato@fastly.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.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