• Maciej Lipinski's avatar
    [issue #201] moved update of age-time within mutex · 85a7069b
    Maciej Lipinski authored
    The problem was as follows:
    - there were two nodes with the same MAC address, sending traffic
      at high frequency
    - the above triggers a lot of learning requests to rtud, as a result
    - rtu HASH table representation in SHMEM is constantly udpated
    - the aging process runs in background (separate process) and updates
      the time the entry was last used.
    
    The update process could not the time of last access in the HASH
    table in SHMEM because the learing process was constantly occupying
    the SHMEM. The age out process was never aging out entry (even if this
    one is within mutex) since the access time was never updated.
    
    Thus, now both, update of last access time and age-out process are
    both within mutex that allows the learning and aging-out processes
    to both access SHMEM and HW.
    85a7069b
Name
Last commit
Last update
binaries Loading commit data...
build Loading commit data...
configs Loading commit data...
doc Loading commit data...
hwinfo-sdb Loading commit data...
kernel Loading commit data...
patches Loading commit data...
robustness/coding Loading commit data...
scripts Loading commit data...
usb-loader Loading commit data...
userspace Loading commit data...
.gitignore Loading commit data...
.gitmodules Loading commit data...
COPYING Loading commit data...
Kconfig Loading commit data...
Kconfig_port_timing.in Loading commit data...
Kconfig_sfp_fiber.in Loading commit data...
Kconfig_vlans.in Loading commit data...
Makefile Loading commit data...
Makefile.kconfig Loading commit data...
README Loading commit data...
gen_kconfig_port_timing.sh Loading commit data...
gen_kconfig_sfp_fiber.sh Loading commit data...