Hi! On Mon 2017-09-18 20:27:13, tristram...@microchip.com wrote: > > > +/** > > > + * Some counters do not need to be read too often because they are less > > likely > > > + * to increase much. > > > + */ > > > > What does comment mean? Are you caching statistics, and updating > > different values at different rates? > > > > There are 34 counters. In normal case using generic bus I/O or PCI to read > them > is very quick, but the switch is mostly accessed using SPI, or even I2C. As > the SPI > access is very slow and cannot run in interrupt context I keep worrying > reading > the MIB counters in a loop for 5 or more ports will prevent other critical > hardware > access from executing soon enough. These accesses can be getting 1588 PTP > timestamps and opening/closing ports. (RSTP Conformance Test sends test > traffic > to port supposed to be closed/opened after receiving specific RSTP > BPDU.)
Hmm. Ok, interesting.
I wonder how well this is going to work if userspace actively 'does
something' with the switch.
It seems to me that even if your statistics code is careful not to do
'a lot' of accesses at the same time, userspace can use other parts of
the driver to do the same, and thus cause same unwanted effects...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
signature.asc
Description: Digital signature
