From: Jakub Kicinski <kuba@kernel.org>
To: "Maciej Żenczykowski" <maze@google.com>,
"Florian Fainelli" <f.fainelli@gmail.com>
Cc: "Maciej Żenczykowski" <zenczykowski@gmail.com>,
"Linux Network Development Mailing List" <netdev@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Paolo Abeni" <pabeni@redhat.com>,
"Kory Maincent (Dent Project)" <kory.maincent@bootlin.com>,
"Ahmed Zaki" <ahmed.zaki@intel.com>,
"Edward Cree" <ecree.xilinx@gmail.com>,
"Yuyang Huang" <yuyanghuang@google.com>,
"Lorenzo Colitti" <lorenzo@google.com>
Subject: Re: [PATCH net-next] ethtool: add tunable api to disable various firmware offloads
Date: Wed, 14 Aug 2024 17:32:48 -0700 [thread overview]
Message-ID: <20240814173248.685681d7@kernel.org> (raw)
In-Reply-To: <20240813223325.3522113-1-maze@google.com>
On Tue, 13 Aug 2024 15:33:25 -0700 Maciej Żenczykowski wrote:
> In order to save power (battery), most network hardware
> designed for low power environments (ie. battery powered
> devices) supports varying types of hardware/firmware offload
> (filtering and/or generating replies) of incoming packets.
>
> The goal being to prevent device wakeups caused by ingress 'spam'.
>
> This is particularly true for wifi (especially phones/tablets),
> but isn't actually wifi specific. It can also be implemented
> in wired nics (TV) or usb ethernet dongles.
>
> For examples TVs require this to keep power consumption
> under (the EU mandated) 2 Watts while idle (display off),
> while still being discoverable on the network.
Sounds sane, adding Florian, he mentioned MDNS at last netconf.
Tho, wasn't there supposed to be a more granular API in Android
to control such protocol offloads?
You gotta find an upstream driver which implements this for us to merge.
If Florian doesn't have any quick uses -- I think Intel ethernet drivers
have private flags for enabling/disabling an LLDP agent. That could be
another way..
--
pw-bot: cr
next prev parent reply other threads:[~2024-08-15 0:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 22:33 [PATCH net-next] ethtool: add tunable api to disable various firmware offloads Maciej Żenczykowski
2024-08-15 0:32 ` Jakub Kicinski [this message]
2024-08-15 3:08 ` Florian Fainelli
2024-08-15 15:45 ` Jakub Kicinski
2024-08-15 16:38 ` Florian Fainelli
2024-08-16 0:49 ` Maciej Żenczykowski
2024-08-16 17:51 ` Jakub Kicinski
2024-08-15 16:13 ` Nelson, Shannon
2024-08-16 0:55 ` Maciej Żenczykowski
2024-08-16 1:03 ` Nelson, Shannon
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=20240814173248.685681d7@kernel.org \
--to=kuba@kernel.org \
--cc=ahmed.zaki@intel.com \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=lorenzo@google.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yuyanghuang@google.com \
--cc=zenczykowski@gmail.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;
as well as URLs for NNTP newsgroup(s).