On Wed, May 29, 2019 at 09:48:02AM +0200, Jens Freimann wrote: > On Tue, May 28, 2019 at 10:40:42PM -0400, Michael S. Tsirkin wrote: > > On Tue, May 21, 2019 at 08:49:18PM +0200, Jens Freimann wrote: > > > On Tue, May 21, 2019 at 07:37:19AM -0400, Michael S. Tsirkin wrote: > > > > On Tue, May 21, 2019 at 09:21:57AM +0200, Jens Freimann wrote: > > > > Actually is there a list of devices for which this has been tested > > > > besides mlx5? I think someone said some old intel cards > > > > don't support this well, we might need to blacklist these ... > > > > > > So far I've tested mlx5 and XL710 which both worked, but I'm > > > working on testing with more devices. But of course help with testing > > > is greatly appreciated. > > > > A testing tool that people can run to get a pass/fail > > result would be needed for that. > > Do you have something like this? > > I have two simple tools. One that sends packets and another one that > sniffs for packets to see which device the packet goes to. Find it at > https://github.com/jensfr/netfailover_driver_detect > > Feedback and/or patches welcome. > > regards, > Jens
The docs say: ./is_legacy -d . If is_legacy returns 0 it means it has received the packets sent by send_packet. If it returns 1 it didn't receive the packet. Now run ./is_legacy -d So -d twice. What is the difference? -- MST