[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240814173248.685681d7@kernel.org>
Date: Wed, 14 Aug 2024 17:32:48 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: "Maciej Żenczykowski" <maze@...gle.com>, Florian
Fainelli <f.fainelli@...il.com>
Cc: "Maciej Żenczykowski" <zenczykowski@...il.com>,
Linux Network Development Mailing List <netdev@...r.kernel.org>, "David S .
Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo
Abeni <pabeni@...hat.com>, "Kory Maincent (Dent Project)"
<kory.maincent@...tlin.com>, Ahmed Zaki <ahmed.zaki@...el.com>, Edward Cree
<ecree.xilinx@...il.com>, Yuyang Huang <yuyanghuang@...gle.com>, Lorenzo
Colitti <lorenzo@...gle.com>
Subject: Re: [PATCH net-next] ethtool: add tunable api to disable various
firmware offloads
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
Powered by blists - more mailing lists