search for: resnulli

Displaying 20 results from an estimated 124 matches for "resnulli".

[PATCH net-next v9 2/4] net: Introduce generic failover module
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 fa...
[PATCH net-next v9 2/4] net: Introduce generic failover module
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 fa...
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
On Tue, May 22, 2018 at 11:08:53AM +0200, Jiri Pirko wrote: > Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: > >Tue, May 22, 2018 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...
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
On Tue, May 22, 2018 at 11:08:53AM +0200, Jiri Pirko wrote: > Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: > >Tue, May 22, 2018 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...
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
3
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
Tue, May 22, 2018 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,
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
3
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
Tue, May 22, 2018 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,
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
On Tue, May 22, 2018 at 03:14:22PM +0200, Jiri Pirko wrote: > Tue, May 22, 2018 at 03:12:40PM CEST, mst at redhat.com wrote: > >On Tue, May 22, 2018 at 11:08:53AM +0200, Jiri Pirko wrote: > >> Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: > >> >Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudrala at intel.com wrote: > >> >>Use the registration/notification framework supported by the generic > >> >>failover infrastructure. > >> >> > >> >>Signed-off-b...
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
On Tue, May 22, 2018 at 03:14:22PM +0200, Jiri Pirko wrote: > Tue, May 22, 2018 at 03:12:40PM CEST, mst at redhat.com wrote: > >On Tue, May 22, 2018 at 11:08:53AM +0200, Jiri Pirko wrote: > >> Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: > >> >Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudrala at intel.com wrote: > >> >>Use the registration/notification framework supported by the generic > >> >>failover infrastructure. > >> >> > >> >>Signed-off-b...
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
2018 Feb 21
6
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
On Wed, Feb 21, 2018 at 11:38 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 06:56:35PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Wed, Feb 21, 2018 at 05:49:49PM CET, alexander.duyck at gmail.com wrote: >>>>On Wed, Feb 21, 20...
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
2018 Feb 21
6
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
On Wed, Feb 21, 2018 at 11:38 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 06:56:35PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Wed, Feb 21, 2018 at 05:49:49PM CET, alexander.duyck at gmail.com wrote: >>>>On Wed, Feb 21, 20...
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
On 5/22/2018 2:08 AM, Jiri Pirko wrote: > Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: >> Tue, May 22, 2018 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...
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
2018 Feb 21
2
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
On Wed, Feb 21, 2018 at 8:11 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 04:56:48PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 1:51 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Tue, Feb 20, 2018 at 11:33:56PM CET, kubakici at wp.pl wrote: >>>>On Tue, 20 Feb 2018 21:14:10...
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
2018 Feb 21
2
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
On Wed, Feb 21, 2018 at 8:11 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 04:56:48PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 1:51 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Tue, Feb 20, 2018 at 11:33:56PM CET, kubakici at wp.pl wrote: >>>>On Tue, 20 Feb 2018 21:14:10...
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
2018 Feb 21
2
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 05:49:49PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 8:11 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Wed, Feb 21, 2018 at 04:56:48PM CET, alexander.duyck at gmail.com wrote: >>>>On Wed, Feb 21, 20...
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
2018 Feb 21
2
[RFC PATCH v3 0/3] Enable virtio_net to act as a backup for a passthru device
On Wed, Feb 21, 2018 at 8:58 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Wed, Feb 21, 2018 at 05:49:49PM CET, alexander.duyck at gmail.com wrote: >>On Wed, Feb 21, 2018 at 8:11 AM, Jiri Pirko <jiri at resnulli.us> wrote: >>> Wed, Feb 21, 2018 at 04:56:48PM CET, alexander.duyck at gmail.com wrote: >>>>On Wed, Feb 21, 20...
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...wrote: > >On Tue, May 22, 2018 at 03:14:22PM +0200, Jiri Pirko wrote: > >> Tue, May 22, 2018 at 03:12:40PM CEST, mst at redhat.com wrote: > >> >On Tue, May 22, 2018 at 11:08:53AM +0200, Jiri Pirko wrote: > >> >> Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: > >> >> >Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudrala at intel.com wrote: > >> >> >>Use the registration/notification framework supported by the generic > >> >> >>failover infrastructure. > >> >> >&gt...
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...wrote: > >On Tue, May 22, 2018 at 03:14:22PM +0200, Jiri Pirko wrote: > >> Tue, May 22, 2018 at 03:12:40PM CEST, mst at redhat.com wrote: > >> >On Tue, May 22, 2018 at 11:08:53AM +0200, Jiri Pirko wrote: > >> >> Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: > >> >> >Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudrala at intel.com wrote: > >> >> >>Use the registration/notification framework supported by the generic > >> >> >>failover infrastructure. > >> >> >&gt...
[PATCH net-next v9 2/4] net: Introduce generic failover module
2018 May 02
1
[PATCH net-next v9 2/4] net: Introduce generic failover module
On Wed, May 02, 2018 at 10:51:12AM -0700, Samudrala, Sridhar wrote: > > > On 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); &gt...
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
2018 May 22
2
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
On Tue, May 22, 2018 at 05:36:14PM +0200, Jiri Pirko wrote: > Tue, May 22, 2018 at 05:28:42PM CEST, sridhar.samudrala at intel.com wrote: > > > >On 5/22/2018 2:08 AM, Jiri Pirko wrote: > >> Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: > >> > Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudrala at intel.com wrote: > >> > > Use the registration/notification framework supported by the generic > >> > > failover infrastructure. > >> > > > >> > > Sig...
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
2018 May 22
2
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
On Tue, May 22, 2018 at 05:36:14PM +0200, Jiri Pirko wrote: > Tue, May 22, 2018 at 05:28:42PM CEST, sridhar.samudrala at intel.com wrote: > > > >On 5/22/2018 2:08 AM, Jiri Pirko wrote: > >> Tue, May 22, 2018 at 11:06:37AM CEST, jiri at resnulli.us wrote: > >> > Tue, May 22, 2018 at 04:06:18AM CEST, sridhar.samudrala at intel.com wrote: > >> > > Use the registration/notification framework supported by the generic > >> > > failover infrastructure. > >> > > > >> > > Sig...