public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: Jakub Kicinski <kuba@kernel.org>, Heng Qi <hengqi@linux.alibaba.com>
Cc: netdev@vger.kernel.org, jgg@nvidia.com, leonro@nvidia.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Tal Gilboa <talgi@nvidia.com>,
	"open list:LIBRARY CODE" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] lib: Allow for the DIM library to be modular
Date: Thu, 2 May 2024 20:19:27 -0700	[thread overview]
Message-ID: <60ac51d1-da8a-4108-97c0-2d1ca8dc997e@broadcom.com> (raw)
In-Reply-To: <20240502175815.4f1619c6@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1832 bytes --]

+CC Heng,

On 5/2/2024 5:58 PM, Jakub Kicinski wrote:
> On Thu,  2 May 2024 17:25:40 -0700 Florian Fainelli wrote:
>> Allow the Dynamic Interrupt Moderation (DIM) library to be built as a
>> module. This is particularly useful in an Android GKI (Google Kernel
>> Image) configuration where everything is built as a module, including
>> Ethernet controller drivers. Having to build DIMLIB into the kernel
>> image with potentially no user is wasteful.
> 
> How big is it? Folks from Alibaba are trying to add the ability to
> change the profiles, they'd need to change the calling conventions.
> Which is not terrible, but also why make them suffer if the gain
> isn't big..

It is not too big (16KB as a module), however the issue is more 
logistical than the overall size of the kernel image (although that 
might be a concern, too).

The GKI default configuration would have to enable CONFIG_DIMLIB=y 
regardless of whether a driver makes use of it. They would not enable 
any hardware specific modules (e.g.: CONFIG_BCMGENET=m, CONFIG_STMMAC=m) 
in their configuration that is not common to a large number of 
platforms. So the result is that you end up with code being built-in 
that is potentially not used, and you may not have visibility into its 
usage because the model makes it that SoC vendors can built their 
modules against the GKI configuration. Arguably we can solve that within 
our "overlay" at the source level, but I would rather maintain as fewer 
patches as possible and it does not take away anything IMHO.

Looking at "[PATCH net-next v11 0/4] ethtool: provide the dim profile 
fine-tuning channel" it seems like Heng took care of making all of the 
newly added functions EXPORT_SYMBOL(). The only thing I see missing is a 
"select DIMLIB" from config ETHTOOL_NETLINK, do you see something else?
-- 
Florian

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4221 bytes --]

  reply	other threads:[~2024-05-03  3:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  0:25 [PATCH net-next] lib: Allow for the DIM library to be modular Florian Fainelli
2024-05-03  0:58 ` Jakub Kicinski
2024-05-03  3:19   ` Florian Fainelli [this message]
2024-05-03 21:36     ` Jakub Kicinski
2024-05-04 20:16 ` Simon Horman

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=60ac51d1-da8a-4108-97c0-2d1ca8dc997e@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=akpm@linux-foundation.org \
    --cc=hengqi@linux.alibaba.com \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=talgi@nvidia.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