[eepro100] Transmitter Timeout -- addednum
Kallol Biswas
kallol@bugula.fpk.hp.com
Wed, 02 Aug 2000 10:02:31 EDT
Donald,
I guess I have to discuss my design to answer you, but I am not allowed
to do so.
The commands should be executed immediately, there is no doubt about
it, but what if the rate of incoming requests is greater than the rate
of service? BTW, do you know if anybody has modelled the network trafiic
with Markov's process(Queueing theory), I am thinking of applying M/D/1 model.
Regards,
Kallol
>
> I'm not certain what you mean by this: when it's time to do a command, it
> must be done immediately, not after the command unit reaches the end of the
> command ring. For instance, a multicast list change on a machine that isn't
> transmitting should still take place immediately.
>
> > BTW, how frequently do you send the multicast workaround for receiver lockup
> > bug? If the receiver is idle for two seconds and you have rx_bug set, right?
>
> Correct. This bug is presumably fixed in the current hardware, the EEPROM
> bits indicating the error exists are still set.
>
> Donald Becker becker@scyld.com
> Scyld Computing Corporation http://www.scyld.com
> 410 Severn Ave. Suite 210 Beowulf Clusters / Linux Installations
> Annapolis MD 21403
>
>
--
Phone: 973-443-7469 | Design Engineer
Telnet: 1-443-7469 | Operating System Lab
www.kallolbiswas.com | Hewlett Packard Company
kallol_biswas@hp.com | Florham Park, NJ