search for: netdev_rx_handler_regist

Displaying 20 results from an estimated 73 matches for "netdev_rx_handler_regist".

2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...m wrote: >>> Use the registration/notification framework supported by the generic >>> failover infrastructure. >>> >>> Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> >> 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 t...
2018 May 02
4
[PATCH net-next v9 2/4] net: Introduce generic failover module
Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: [...] >>+ >>+ err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>+ failover_dev); >>+ if (err) { >>+ netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n", >>+ err); >>+ goto err_handler_register; >>+ } >>+ >>+ err = netdev_upper_de...
2018 May 22
2
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
...ation framework supported by the generic > >> > > failover infrastructure. > >> > > > >> > > Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > >> > 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 mi...
2018 May 02
4
[PATCH net-next v9 2/4] net: Introduce generic failover module
Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: >Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: [...] >>+ >>+ err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, >>+ failover_dev); >>+ if (err) { >>+ netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n", >>+ err); >>+ goto err_handler_register; >>+ } >>+ >>+ err = netdev_upper_de...
2018 May 22
2
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
...ation framework supported by the generic > >> > > failover infrastructure. > >> > > > >> > > Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > >> > 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 mi...
2018 May 22
3
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...18 at 04:06:18AM CEST, sridhar.samudrala at intel.com wrote: >Use the registration/notification framework supported by the generic >failover infrastructure. > >Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> 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.
2018 May 22
3
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...18 at 04:06:18AM CEST, sridhar.samudrala at intel.com wrote: >Use the registration/notification framework supported by the generic >failover infrastructure. > >Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> 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.
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...by the generic >>>>>>> failover infrastructure. >>>>>>> >>>>>>> Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> >>>>>> 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...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...by the generic >>>>>>> failover infrastructure. >>>>>>> >>>>>>> Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> >>>>>> 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...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...t; >>Use the registration/notification framework supported by the generic > >>failover infrastructure. > >> > >>Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > > > >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. > > > > Also note that in the current patchset you use IFF_FAILOVER flag for > master, yet for the...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...t; >>Use the registration/notification framework supported by the generic > >>failover infrastructure. > >> > >>Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > > > >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. > > > > Also note that in the current patchset you use IFF_FAILOVER flag for > master, yet for the...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...work supported by the generic > >> >>failover infrastructure. > >> >> > >> >>Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > >> > > >> >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. > >> > > >> > >> Also note that in the current patchset...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...work supported by the generic > >> >>failover infrastructure. > >> >> > >> >>Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > >> > > >> >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. > >> > > >> > >> Also note that in the current patchset...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...gt;>failover infrastructure. > >> >> >> > >> >> >>Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > >> >> > > >> >> >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. > >> >> > > >> >> > &gt...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...gt;>failover infrastructure. > >> >> >> > >> >> >>Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > >> >> > > >> >> >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. > >> >> > > >> >> > &gt...
2018 May 22
0
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
...registration/notification framework supported by the generic >> > > failover infrastructure. >> > > >> > > Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> >> > 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 &gt...
2018 May 02
1
[PATCH net-next v9 2/4] net: Introduce generic failover module
...n 5/2/2018 9:15 AM, Jiri Pirko wrote: > > Sat, Apr 28, 2018 at 11:06:01AM CEST, jiri at resnulli.us wrote: > > > Fri, Apr 27, 2018 at 07:06:58PM CEST, sridhar.samudrala at intel.com wrote: > > [...] > > > > > > > > + > > > > + err = netdev_rx_handler_register(slave_dev, net_failover_handle_frame, > > > > + failover_dev); > > > > + if (err) { > > > > + netdev_err(slave_dev, "can not register failover rx handler (err = %d)\n", > > > > + err); > > > > + goto err_handler_reg...
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...orted by the generic >> >> > > failover infrastructure. >> >> > > >> >> > > Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> >> >> > 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 pa...
2018 May 23
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...> failover infrastructure. >> > > > > > > >> > > > > > > Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> >> > > > > > 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 Stephe...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...>> >> >> > >> >> >> >>Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > >> >> >> > > >> >> >> >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. > >> >> >> &...