On Sun, Nov 23, 2014 at 13:39 +0100, Claudio Jeker wrote:
On Sun, Nov 23, 2014 at 02:10:24AM +0100, Mike Belopuhov wrote:
Hi,
This removes the system wide if_slowtimo timeout and lets every
interface with a valid if_watchdog method register it's own.
The rational is to get rid of the
On Sun, Nov 23, 2014 at 12:06 +0100, Martin Pieuchot wrote:
On 23/11/14(Sun) 02:10, Mike Belopuhov wrote:
Hi,
This removes the system wide if_slowtimo timeout and lets every
interface with a valid if_watchdog method register it's own.
The rational is to get rid of the ifnet loop in the
On 23/11/14(Sun) 02:10, Mike Belopuhov wrote:
Hi,
This removes the system wide if_slowtimo timeout and lets every
interface with a valid if_watchdog method register it's own.
The rational is to get rid of the ifnet loop in the softclock
context to avoid further complications with concurrent
On Sun, Nov 23, 2014 at 02:10:24AM +0100, Mike Belopuhov wrote:
Hi,
This removes the system wide if_slowtimo timeout and lets every
interface with a valid if_watchdog method register it's own.
The rational is to get rid of the ifnet loop in the softclock
context to avoid further
Hi,
This removes the system wide if_slowtimo timeout and lets every
interface with a valid if_watchdog method register it's own.
The rational is to get rid of the ifnet loop in the softclock
context to avoid further complications with concurrent access
to the ifnet list. This might also save
On Sun, Nov 23, 2014 at 02:10 +0100, Mike Belopuhov wrote:
Hi,
This removes the system wide if_slowtimo timeout and lets every
interface with a valid if_watchdog method register it's own.
The rational is to get rid of the ifnet loop in the softclock
context to avoid further complications
Now that I think of it, perhaps I should have called it if_slowtimo like
the function. Any preference?
Yes perhaps, because watchdog has connotation in our kernel tree.
