PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Forums Hébergement > Forum Noms de domaine > comp.protocols.tcp-ip > Stack behavior after coming back from hibernation
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
comp.protocols.tcp-ip TCP and IP network protocols.

Stack behavior after coming back from hibernation

Réponse
 
LinkBack Outils de la discussion
Vieux 25/03/2006, 18h47   #1
debdut
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Stack behavior after coming back from hibernation

We are running a customized TCP/IP stack on Windows. The problem is how
do deal with the case of hibernation with respect to the stack timers.
There are 3 possible ways :

1. To do nothing
2. To jump the clock to the real time after coming back from
hibernation. In this case most of
the TCP timers are going to time out (assuming the hibernation time
is long enough) and
behavior is that of the timers suddenly timing out.
3. To fast forward the clock, that is actually run the TCP/IP timers
faster, so that all the events
that would have actually been trigerred by the timers during
hibernation would be compressed
in a very small amount of time, possibly resulting in a flurry of
retransmit segments or
keep-alives.

I wonder how windows deals with the situation, and what could be
relative pros/cons of these
approaches..

Can anybody ?

--Deb

  Réponse avec citation
Vieux 26/03/2006, 06h26   #2
Skybuck Flying
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Stack behavior after coming back from hibernation

Here is an idea:

Store the time when hibernation occured.

Determine the time when it resumed from hibernation.

Calculate the interval.

Add the interval to all timers, timestamps etc.

Bye,
Skybuck.

"debdut" <debdut@gmail.com> wrote in message
news:1143312423.004991.260760@v46g2000cwv.googlegr oups.com...
> We are running a customized TCP/IP stack on Windows. The problem is how
> do deal with the case of hibernation with respect to the stack timers.
> There are 3 possible ways :
>
> 1. To do nothing
> 2. To jump the clock to the real time after coming back from
> hibernation. In this case most of
> the TCP timers are going to time out (assuming the hibernation time
> is long enough) and
> behavior is that of the timers suddenly timing out.
> 3. To fast forward the clock, that is actually run the TCP/IP timers
> faster, so that all the events
> that would have actually been trigerred by the timers during
> hibernation would be compressed
> in a very small amount of time, possibly resulting in a flurry of
> retransmit segments or
> keep-alives.
>
> I wonder how windows deals with the situation, and what could be
> relative pros/cons of these
> approaches..
>
> Can anybody ?
>
> --Deb
>



  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 12h21.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,08510 seconds with 10 queries