On Wed, Jul 22, 2020 at 11:59:09PM -0700, Chi Song wrote: > An imbalanced TX indirection table causes netvsc to have low > performance. This table is created and managed during runtime. To help > better diagnose performance issues caused by imbalanced tables, it needs > make TX indirection tables visible. > > Because TX indirection table is driver specified information, so > display it via ethtool register dump. Is the Tx indirection table really unique to netvsc or can we expect other drivers to support similar feature? Also, would it make sense to allow also setting the table with ethtool? (AFAICS it can be only set from hypervisor at the moment.) It kind of feels that the actual reason for using register dump was that it's there and it was easy to use rather than that the information would logically belong there. We already have a specific interface for getting and seting receive indirection table; perhaps it would make sense to have also one for the transmit indirection table. Michal
