lwIP - A Lightweight TCP/IP stack - Patches: patch #9798, IGMP and MLD6 Timers on demand
You are not allowed to post comments on this tracker with your current authentication level.
patch #9798: IGMP and MLD6 Timers on demand
Submitter: | Sachin Parekh <sachin0x18> | ||
Submitted: | Mon 22 Apr 2019 02:07:11 PM UTC | ||
Category: | Contrib | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Assigned to: | None | Open/Closed: | Open |
Planned Release: | None |
Attached Files
file #46810: 0001-igmp-Option-for-IGMP-Timer-to-be-called-ondemand-dyn.patch added by sachin0x18 (5KiB - application/octet-stream)
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-04-22 | sachin0x18 | Attached File | - | ![]() |
Added 0001-igmp-Option-for-IGMP-Timer-to-be-called-ondemand-dyn.patch, #46810 |
The thought behind this patch is to reduce power consumption when running in low power mode.
The current implementation of IGMP and MLD6 Timer is that they are periodically fired at an interval of 100ms each.
Timer interrupt is called when the timeout expires. The timer interrupt function checks if there are any multicast group timeout running, if so then decrement the timeout value and if it reaches zero then send an appropriate report packet on the network.
The timer restarts itself even if there are no multicast group timeouts. This leads to increase in power consumption. Starting the timer only when receiving a QUERY packet or joining a group will reduce the power consumption.