gigabit ethernet power consumption
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 9 lines · Auke
Quoted 6 lines · K.Prasad
Without the side-effect of experiencing a link-flap when switching to a lower-speed (with its toll in terms of down-time for auto-negotiation, STP, etc), the Interrupt Moderation Algorithm dynamically adjusts the number of interrupts based on traffic - and presumably consume less power. For an "Optimise for Power" kind of profile - the driver can be loaded with a higher throttle rate during boot-time.
Quoted 8 lines
We're changing this to be run-time adjustable in newer drivers.
However, the power consumed by your nic staying in gigabit mode is much greater in the long run then what you can save by trying to scrounge for milliwatts reducing interrupts generated by the nic. By default it already moderates them somewhat. Practically this feature is really not useful for powersaving, it just won't add up to actual benefits in a real life situtation I think.
Just a thought:
How much power does a non-connected NIC consume, and can you save power by forcing 10 MBit until a link is detected (doubling negotiation time)?
Signature · 4 lines
Top 100 things you don't want the sysadmin to say: 22. hey, what does mkfs do? Friß, Spammer: [email protected]
Quoted 18 lines · Bodo Eggert
Quoted 8 lines · Auke
Quoted 6 lines · K.Prasad
Without the side-effect of experiencing a link-flap when switching to a lower-speed (with its toll in terms of down-time for auto-negotiation, STP, etc), the Interrupt Moderation Algorithm dynamically adjusts the number of interrupts based on traffic - and presumably consume less power. For an "Optimise for Power" kind of profile - the driver can be loaded with a higher throttle rate during boot-time.
Quoted 8 lines
We're changing this to be run-time adjustable in newer drivers.
However, the power consumed by your nic staying in gigabit mode is much greater in the long run then what you can save by trying to scrounge for milliwatts reducing interrupts generated by the nic. By default it already moderates them somewhat. Practically this feature is really not useful for powersaving, it just won't add up to actual benefits in a real life situtation I think.
Quoted 3 lines
Just a thought:
How much power does a non-connected NIC consume, and can you save power by forcing 10 MBit until a link is detected (doubling negotiation time)?
no, the PHY consumes a minimal amount of energy when not connected, regardless of whether it is advertising 10, 100 or 1000mbit.
Cheers,
Auke
Quoted 5 lines · Auke
Quoted 2 lines
How much power does a non-connected NIC consume, and can you save power by forcing 10 MBit until a link is detected (doubling negotiation time)?
no, the PHY consumes a minimal amount of energy when not connected, regardless of whether it is advertising 10, 100 or 1000mbit.
Is that true for essentially all the chipsets we support (or at least "the vast majority of the ones currently found in common machines")?
Quoted 9 lines · [email protected] wrote:
Quoted 4 lines · Auke
Quoted 2 lines
How much power does a non-connected NIC consume, and can you save power by forcing 10 MBit until a link is detected (doubling negotiation time)?
no, the PHY consumes a minimal amount of energy when not connected, regardless of whether it is advertising 10, 100 or 1000mbit.
Is that true for essentially all the chipsets we support (or at least "the vast majority of the ones currently found in common machines")?
I would assume that that is true for all PHY's - if there is no link to keep the carrier active on I would think that the power consumption is nominal across the board. Once the PHY detects link pulses it should obviously use different power levels to negotiate the link for each speed.
PHY autonegotiation just works the same across the board - the PHY's send out little pulses (iow nominal power consumption) to detect a link partner, and only when one is found do they engage in more aggressive conversation to establish capabilities across the link.
Auke
Quoted 9 lines · Auke
I would assume that that is true for all PHY's - if there is no link to keep the carrier active on I would think that the power consumption is nominal across the board. Once the PHY detects link pulses it should obviously use different power levels to negotiate the link for each speed.
PHY autonegotiation just works the same across the board - the PHY's send out little pulses (iow nominal power consumption) to detect a link partner, and only when one is found do they engage in more aggressive conversation to establish capabilities across the link.
Too bad not much can be done about fibre ports, but then again you can't even change speeds on those. Then again those are not on laptops or other low power devices in the first place.
--
Len Sorensen
Quoted 6 lines · Lennart Sorensen
Quoted 5 lines · Auke
I would assume that that is true for all PHY's - if there is no link to keep the carrier active on I would think that the power consumption is nominal across the board. Once the PHY detects link pulses it should obviously use different power levels to negotiate the link for each speed.
Quoted 8 lines
Quoted 4 lines
PHY autonegotiation just works the same across the board - the PHY's send out little pulses (iow nominal power consumption) to detect a link partner, and only when one is found do they engage in more aggressive conversation to establish capabilities across the link.
Too bad not much can be done about fibre ports, but then again you can't even change speeds on those. Then again those are not on laptops or other low power devices in the first place.
the only thing we do for fiber ports is power off the laser if the user explicitly powers them down at shutdown. Note that WoL needs to be disabled for that.
Auke