netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: netdev@vger.kernel.org
Subject: [ANN] netdev development stats for 6.19
Date: Tue, 2 Dec 2025 17:55:48 -0800	[thread overview]
Message-ID: <20251202175548.6b5eb80e@kernel.org> (raw)

Hi!

Intro
-----

As is tradition here are the development statistics based on mailing
list traffic on netdev@vger.

These stats are somewhat like LWN stats: https://lwn.net/Articles/1004998/
but more focused on mailing list participation. And by participation
we mean reviewing code more than producing patches.

In particular "review score" tries to capture the balance between
reviewing other people's code vs posting patches. It's roughly
number of patches reviewed minus number of patches posted. 
Those who post more than they review will have a negative score.

Previous 3 reports:
 - for 6.16: https://lore.kernel.org/20250529144354.4ca86c77@kernel.org
 - for 6.17: https://lore.kernel.org/20250728160647.6d0bb258@kernel.org
 - for 6.18: https://lore.kernel.org/20251002171032.75263b18@kernel.org 

General stats
-------------

This release cycle was 6% smaller in terms of postings and 15% smaller 
in terms of merged commits than 6.18. We have also regressed in terms
of review coverage. 

Personally, this cycle felt quite busy for me. netdev foundation
received its first batch of servers, and the infrastructure has been
mostly migrated over to those (the UI still runs on the old setup but
builds and kselftests run on the shiny new machines). "We" have also
spent some time integrating the AI code review built by Chris Mason. 

Looking ahead we are expecting more server deliveries, including some
400GE NICs for the community to experiment with. The netdev foundation
still has a good chunk of money left so please do not hesitate to
suggest how we can spend it to improve the project and help developers.

Developer rankings
------------------

Contributions to selftests:
   1 [ 30] Jakub Kicinski
   2 [ 24] Matthieu Baerts
   3 [ 13] Bobby Eshleman
   4 [  6] Carolina Jubran
   5 [  4] Kuniyuki Iwashima
   6 [  3] Eric Dumazet
   7 [  3] Breno Leitao

Top reviewers (cs):                  Top reviewers (msg):                
   1 (   ) [28] Jakub Kicinski          1 (   ) [61] Jakub Kicinski      
   2 (   ) [21] Simon Horman            2 (   ) [41] Andrew Lunn         
   3 (   ) [14] Andrew Lunn             3 (   ) [38] Simon Horman        
   4 (   ) [ 9] Paolo Abeni             4 (   ) [21] Paolo Abeni         
   5 (+27) [ 5] Maxime Chevallier       5 (***) [13] Maxime Chevallier   
   6 ( -1) [ 5] Eric Dumazet            6 ( +1) [13] Russell King        
   7 ( -1) [ 5] Russell King            7 ( +6) [12] Aleksandr Loktionov 
   8 ( +1) [ 5] Aleksandr Loktionov     8 ( -3) [12] Eric Dumazet        
   9 ( +3) [ 4] Jacob Keller            9 ( +3) [10] Michael S. Tsirkin  
  10 ( -2) [ 4] Kuniyuki Iwashima      10 (+35) [10] Stefano Garzarella  
  11 (+30) [ 3] Sabrina Dubroca        11 ( +5) [ 9] Jacob Keller        
  12 ( -5) [ 3] Vadim Fedorenko        12 (+14) [ 8] Sabrina Dubroca     
  13 (+24) [ 2] Alexander Lobakin      13 ( -5) [ 7] Kuniyuki Iwashima   
  14 ( +1) [ 2] Vladimir Oltean        14 (+44) [ 7] Kory Maincent (Dent Project)
  15 ( -5) [ 2] Paul Menzel            15 (***) [ 6] Toke Høiland-Jørgensen

Lots of familiar names in top reviewer ranking. Let me focus on those
with most significant gains. Maxime has helped with various embedded
(stmmac and PHY) reviews (sorry that we didn't manage to merge the
phy_port series in time for 6.19!). Sabrina helped with TLS, IPsec,
OVPN as well as a few core changes. Stefano had his hands full with
vsock changes. Kory reviewed PSE and timestamp NDO conversion patches.
Aleksandr reviewed mostly Intel NIC patches, but occasionally also
patches for other NICs. Alexander (with an e) reviewed some of Eric's
skb optimizations.

Once again, huge thanks to those who help with patch reviews!

Top authors (cs):                    Top authors (msg):                  
   1 ( +1) [5] Eric Dumazet             1 (+12) [35] Christian Brauner   
   2 ( +1) [3] Russell King             2 (   ) [27] Russell King        
   3 ( -2) [3] Jakub Kicinski           3 ( +5) [19] Tariq Toukan        
   4 ( +2) [3] Tariq Toukan             4 (+43) [19] Bobby Eshleman      
   5 ( +2) [3] Heiner Kallweit          5 (+34) [18] Vadim Fedorenko     
   6 ( -1) [2] Alok Tiwari              6 (+27) [16] Maxime Chevallier   
   7 ( +8) [2] Breno Leitao             7 ( +8) [16] Daniel Golle        
   8 (   ) [2] Kuniyuki Iwashima        8 ( -2) [15] Eric Dumazet        
   9 (***) [2] Randy Dunlap             9 (+49) [14] Daniel Jurgens      
  10 (+29) [2] Vadim Fedorenko         10 ( -9) [13] Jakub Kicinski      


Top scores (positive):               Top scores (negative):              
   1 (   ) [412] Jakub Kicinski         1 ( +8) [135] Christian Brauner  
   2 (   ) [306] Simon Horman           2 (+33) [ 74] Bobby Eshleman     
   3 (   ) [256] Andrew Lunn            3 ( +4) [ 67] Tariq Toukan       
   4 (   ) [144] Paolo Abeni            4 (+37) [ 58] Daniel Jurgens     
   5 ( +6) [ 79] Aleksandr Loktionov    5 ( +7) [ 56] Daniel Golle       
   6 (+32) [ 45] Sabrina Dubroca        6 (***) [ 44] Jeff Layton        
   7 (+12) [ 37] Michael S. Tsirkin     7 ( +9) [ 40] Eliav Farber       

Company rankings
----------------

Top reviewers (cs):                  Top reviewers (msg):                
   1 ( +1) [34] RedHat                  1 ( +1) [102] RedHat             
   2 ( -1) [30] Meta                    2 ( -1) [ 76] Meta               
   3 (   ) [17] Intel                   3 ( +2) [ 44] Intel              
   4 (   ) [14] Andrew Lunn             4 (   ) [ 41] Andrew Lunn        
   5 (   ) [11] Google                  5 ( -2) [ 27] Google             
   6 ( +1) [ 9] nVidia                  6 ( +1) [ 20] nVidia             
   7 ( -1) [ 7] Oracle                  7 ( -1) [ 18] Oracle             

Top authors (cs):                    Top authors (msg):                  
   1 (   ) [12] Meta                    1 (   ) [95] Meta                
   2 (   ) [10] RedHat                  2 (   ) [52] RedHat              
   3 (   ) [10] Google                  3 ( +2) [48] nVidia              
   4 (   ) [ 7] Intel                   4 (   ) [47] Intel               
   5 ( +1) [ 7] Oracle                  5 ( +9) [41] Microsoft           
   6 ( -1) [ 7] nVidia                  6 ( -3) [38] Google              
   7 ( +1) [ 3] Huawei                  7 ( -1) [34] Oracle              
       
Top scores (positive):               Top scores (negative):              
   1 ( +1) [438] RedHat                 1 (+14) [137] Microsoft          
   2 ( +1) [256] Andrew Lunn            2 ( +9) [ 56] Daniel Golle       
   3 ( -2) [141] Meta                   3 ( +1) [ 50] nVidia             
   4 (   ) [107] Intel                  4 ( +1) [ 47] Huawei             
   5 ( +2) [ 38] ARM                    5 ( +7) [ 44] Amazon             
   6 ( +6) [ 33] Linux Foundation       6 (+23) [ 40] AMD                
   7 ( -1) [ 31] Google                 7 ( -4) [ 40] Pengutronix        
-- 
Code: https://github.com/kuba-moo/ml-stat
Raw output: https://netdev.bots.linux.dev/static/nipa/stats-6.19/stdout

                 reply	other threads:[~2025-12-03  1:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251202175548.6b5eb80e@kernel.org \
    --to=kuba@kernel.org \
    --cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).