> -----Original Message----- > From: David Miller [mailto:davem@xxxxxxxxxxxxx] > Sent: Friday, June 10, 2016 9:14 PM > To: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx> > Cc: netdev@xxxxxxxxxxxxxxx; KY Srinivasan <kys@xxxxxxxxxxxxx>; > olaf@xxxxxxxxx; vkuznets@xxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; > driverdev-devel@xxxxxxxxxxxxxxxxxxxxxx > Subject: Re: [PATCH net-next,v2] tools: hv: Add a script to help bonding > synthetic and VF NICs > > From: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx> > Date: Fri, 10 Jun 2016 14:23:12 -0700 > > > This script helps to create bonding network devices based on synthetic NIC > > (the virtual network adapter usually provided by Hyper-V) and the > matching > > VF NIC (SRIOV virtual function). So the synthetic NIC and VF NIC can > > function as one network device, and fail over to the synthetic NIC if VF is > > down. > > > > Signed-off-by: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx> > > Reviewed-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx> > > --- > > v2: Make it to be distro neutral. > > This tool doesn't configure anything. > > It fishes information out of sysfs and prints it out. > > I don't think this is useful, not appropriate for the kernel > tools subdirectory at all. > > When I said make it distro neutral, that meant if you wanted to submit > this again you were expected to do the hard work of making it > configure things properly on all major distributions. The major distros supported by Hyper-V include RHEL, SLES, and Ubuntu. I will put them into the configuration scripts -- is this sufficient? Thanks, - Haiyang _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
