> On Wed, 6 May 2020 14:33:08 +0300 Igor Russkikh wrote: >> To implement debug dump retrieval on a live system we add callbacks to >> collect the same data which is collected now during manual `ethtool -d` >> call. >> >> But we instead collect the dump immediately at the moment bad thing >> happens, and save it for later retrieval by the same `ethtool -d`. >> >> To have ability to track this event, we add kobject uevent trigger, >> so udev event handler script could be used to automatically collect > dumps. > > No way. Please use devlink health. Instead of magic ethtool dumps and > custom udev. >
Hi Jakub, Thanks for the suggestion. I've looked into devlink health infrastructure, but what's warned me is that our device health dumps are huge (~3Mb). I'm not sure if health dump infrastructure is designed to push that amounts of data. I'll check if that's feasible. Thanks, Igor
