From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Samudrala, Sridhar" Subject: Re: [PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework Date: Tue, 22 May 2018 08:28:42 -0700 Message-ID: <39081bce-3913-5b07-3d07-0c476fca5e78@intel.com> References: <1526954781-35359-1-git-send-email-sridhar.samudrala@intel.com> <1526954781-35359-3-git-send-email-sridhar.samudrala@intel.com> <20180522090637.GE2149@nanopsycho> <20180522090853.GF2149@nanopsycho> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Cc: mst@redhat.com, stephen@networkplumber.org, davem@davemloft.net, netdev@vger.kernel.org, virtualization@lists.linux-foundation.org, virtio-dev@lists.oasis-open.org, jesse.brandeburg@intel.com, alexander.h.duyck@intel.com, kubakici@wp.pl, jasowang@redhat.com, loseweigh@gmail.com, aaron.f.brown@intel.com, anjali.singhai@intel.com To: Jiri Pirko Return-path: Sender: List-Post: List-Help: List-Unsubscribe: List-Subscribe: In-Reply-To: <20180522090853.GF2149@nanopsycho> Content-Language: en-US List-Id: netdev.vger.kernel.org On 5/22/2018 2:08 AM, Jiri Pirko wrote: > Tue, May 22, 2018 at 11:06:37AM CEST, jiri@resnulli.us wrote: >> Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudrala@intel.com wrote: >>> Use the registration/notification framework supported by the generic >>> failover infrastructure. >>> >>> Signed-off-by: Sridhar Samudrala >> In previous patchset versions, the common code did >> netdev_rx_handler_register() and netdev_upper_dev_link() etc >> (netvsc_vf_join()). Now, this is still done in netvsc. Why? >> >> This should be part of the common "failover" code. Based on Stephen's feedback on earlier patches, i tried to minimize the changes to netvsc and only commonize the notifier and the main event handler routine. Another complication is that netvsc does part of registration in a delayed workqueue. It should be possible to move some of the code from net_failover.c to generic failover.c in future if Stephen is ok with it. >> > Also note that in the current patchset you use IFF_FAILOVER flag for > master, yet for the slave you use IFF_SLAVE. That is wrong. > IFF_FAILOVER_SLAVE should be used. Not sure which code you are referring to.  I only set IFF_FAILOVER_SLAVE in patch 3.