From: Jakub Kicinski <kuba@kernel•org>
To: Heng Qi <hengqi@linux•alibaba.com>
Cc: netdev@vger•kernel.org, virtualization@lists•linux.dev,
"David S . Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Paolo Abeni <pabeni@redhat•com>, Jason Wang <jasowang@redhat•com>,
"Michael S . Tsirkin" <mst@redhat•com>,
Brett Creeley <bcreeley@amd•com>,
Ratheesh Kannoth <rkannoth@marvell•com>,
Alexander Lobakin <aleksander.lobakin@intel•com>,
Xuan Zhuo <xuanzhuo@linux•alibaba.com>,
Tal Gilboa <talgi@nvidia•com>, Jonathan Corbet <corbet@lwn•net>,
linux-doc@vger•kernel.org,
Maxime Chevallier <maxime.chevallier@bootlin•com>,
Jiri Pirko <jiri@resnulli•us>,
Paul Greenwalt <paul.greenwalt@intel•com>,
Ahmed Zaki <ahmed.zaki@intel•com>,
Vladimir Oltean <vladimir.oltean@nxp•com>,
Kory Maincent <kory.maincent@bootlin•com>,
Andrew Lunn <andrew@lunn•ch>,
"justinstitt@google•com" <justinstitt@google•com>
Subject: Re: [PATCH net-next v9 2/4] ethtool: provide customized dim profile management
Date: Wed, 24 Apr 2024 16:59:06 -0700 [thread overview]
Message-ID: <20240424165906.37c83c04@kernel.org> (raw)
In-Reply-To: <df6163de-d82c-458d-b298-1eaf406e6b3d@linux.alibaba.com>
On Thu, 25 Apr 2024 00:49:26 +0800 Heng Qi wrote:
> If I'm not wrong, you don't want an interface
> like .ndo_init_irq_moder, but instead provide a generic interface in
> dim.c (e.g. net_dim_init_irq_moder() with parameters dev and struct
> dim_irq_moder or separate flags,mode,work). Then this func is called
> by the driver in the probe phase?
That's right.
next prev parent reply other threads:[~2024-04-24 23:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 15:55 [PATCH net-next v9 0/4] ethtool: provide the dim profile fine-tuning channel Heng Qi
2024-04-17 15:55 ` [PATCH net-next v9 1/4] linux/dim: move useful macros to .h file Heng Qi
2024-04-17 15:55 ` [PATCH net-next v9 2/4] ethtool: provide customized dim profile management Heng Qi
2024-04-19 0:48 ` Jakub Kicinski
2024-04-22 9:00 ` Heng Qi
2024-04-22 18:39 ` Jakub Kicinski
2024-04-24 13:10 ` Heng Qi
2024-04-24 15:52 ` Jakub Kicinski
2024-04-24 13:41 ` Heng Qi
2024-04-24 16:18 ` Jakub Kicinski
2024-04-24 16:49 ` Heng Qi
2024-04-24 23:59 ` Jakub Kicinski [this message]
2024-04-21 15:53 ` Brett Creeley
2024-04-22 9:04 ` Heng Qi
2024-04-17 15:55 ` [PATCH net-next v9 3/4] virtio-net: refactor dim initialization/destruction Heng Qi
2024-04-17 15:55 ` [PATCH net-next v9 4/4] virtio-net: support dim profile fine-tuning Heng Qi
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=20240424165906.37c83c04@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=ahmed.zaki@intel$(echo .)com \
--cc=aleksander.lobakin@intel$(echo .)com \
--cc=andrew@lunn$(echo .)ch \
--cc=bcreeley@amd$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=hengqi@linux$(echo .)alibaba.com \
--cc=jasowang@redhat$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=justinstitt@google$(echo .)com \
--cc=kory.maincent@bootlin$(echo .)com \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=maxime.chevallier@bootlin$(echo .)com \
--cc=mst@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=paul.greenwalt@intel$(echo .)com \
--cc=rkannoth@marvell$(echo .)com \
--cc=talgi@nvidia$(echo .)com \
--cc=virtualization@lists$(echo .)linux.dev \
--cc=vladimir.oltean@nxp$(echo .)com \
--cc=xuanzhuo@linux$(echo .)alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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