search for: netvsc

Displaying 20 results from an estimated 418 matches for "netvsc".

2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...t;>> >>>>>>> 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...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...t;>> >>>>>>> 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...
2018 Apr 20
6
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...ridhar Samudrala <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> Do what you want to other devices but leave netvsc alone. Adding these failover ops does not reduce the code size, and really is no benefit. The netvsc device driver needs to be backported to several other distributions and doing this makes that harder. I will NAK patches to change to common code for netvsc especially the three device model. MS...
2018 Apr 20
6
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...ridhar Samudrala <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> Do what you want to other devices but leave netvsc alone. Adding these failover ops does not reduce the code size, and really is no benefit. The netvsc device driver needs to be backported to several other distributions and doing this makes that harder. I will NAK patches to change to common code for netvsc especially the three device model. MS...
2018 May 22
2
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
...ructure. > >> > > > >> > > 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 the no...
2018 May 22
2
Shepherd request (P83): Multipath TCP: Present Use Cases and an Upstream Future
...ructure. > >> > > > >> > > 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 the no...
2011 Apr 21
8
[PATCH 0/8] staging: hv: clean up forward declarations and camel cases in netvsc.c
From: haiyangz <haiyangz at hz-dev.msft.interop.novell.com> This patch series cleans up forward declarations and the remaining camel cases in netvsc.c Haiyang Zhang (8): staging: hv: move netvsc_initialize() to clean up forward declaration staging: hv: move netvsc_receive_completion() to clean up forward declaration staging: hv: move netvsc_send_recv_completion() to clean up forward declaration staging: hv: move netvsc_destroy_...
2011 Apr 21
8
[PATCH 0/8] staging: hv: clean up forward declarations and camel cases in netvsc.c
From: haiyangz <haiyangz at hz-dev.msft.interop.novell.com> This patch series cleans up forward declarations and the remaining camel cases in netvsc.c Haiyang Zhang (8): staging: hv: move netvsc_initialize() to clean up forward declaration staging: hv: move netvsc_receive_completion() to clean up forward declaration staging: hv: move netvsc_send_recv_completion() to clean up forward declaration staging: hv: move netvsc_destroy_...
2018 May 23
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...t; > > 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 >&g...
2018 May 22
2
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...upported 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 the notifier and the main event handler routine. Anoth...
2018 May 22
0
[PATCH net-next v11 2/5] netvsc: refactor notifier/event handling code to use the failover framework
...t;> > > >> >> > > 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 o...
2018 Apr 23
3
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...> > >> Use the registration/notification framework supported by the generic > >> failover infrastructure. > >> > >> Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > > > >Do what you want to other devices but leave netvsc alone. > >Adding these failover ops does not reduce the code size, and really is > >no benefit. The netvsc device driver needs to be backported to several > >other distributions and doing this makes that harder. > > We should not care about the backport burden when we ar...
2018 Apr 23
3
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...> > >> Use the registration/notification framework supported by the generic > >> failover infrastructure. > >> > >> Signed-off-by: Sridhar Samudrala <sridhar.samudrala at intel.com> > > > >Do what you want to other devices but leave netvsc alone. > >Adding these failover ops does not reduce the code size, and really is > >no benefit. The netvsc device driver needs to be backported to several > >other distributions and doing this makes that harder. > > We should not care about the backport burden when we ar...
2011 Mar 29
9
[PATCH 00/07] Remove and replace all un-needed DPRINT and printk
This patch set removes all un-needed DPRINT and printk calls and replaces the remaining ones with the correct pr_, dev_ and netdev_ calls from hv_vmbus, hv_netvsc, hv_timesource and hv_utils. Several DPRINTS are remaining that will be cleaned up in my next set of patches. They deal with printing out certain debugging that will be implemented slightly differently. The remaining hv_storvsc and hv_blkvsc will get the same treatment in a different set of patc...
2011 Mar 29
9
[PATCH 00/07] Remove and replace all un-needed DPRINT and printk
This patch set removes all un-needed DPRINT and printk calls and replaces the remaining ones with the correct pr_, dev_ and netdev_ calls from hv_vmbus, hv_netvsc, hv_timesource and hv_utils. Several DPRINTS are remaining that will be cleaned up in my next set of patches. They deal with printing out certain debugging that will be implemented slightly differently. The remaining hv_storvsc and hv_blkvsc will get the same treatment in a different set of patc...
2018 Apr 23
5
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...Mon, 23 Apr 2018 20:24:56 +0300 >> "Michael S. Tsirkin" <mst at redhat.com> wrote: >> >> > On Mon, Apr 23, 2018 at 10:04:06AM -0700, Stephen Hemminger wrote: >> > > > > >> > > > >I will NAK patches to change to common code for netvsc especially the >> > > > >three device model. MS worked hard with distro vendors to support transparent >> > > > >mode, ans we really can't have a new model; or do backport. >> > > > > >> > > > >Plus, DPDK is now dependent...
2018 Apr 23
5
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
...Mon, 23 Apr 2018 20:24:56 +0300 >> "Michael S. Tsirkin" <mst at redhat.com> wrote: >> >> > On Mon, Apr 23, 2018 at 10:04:06AM -0700, Stephen Hemminger wrote: >> > > > > >> > > > >I will NAK patches to change to common code for netvsc especially the >> > > > >three device model. MS worked hard with distro vendors to support transparent >> > > > >mode, ans we really can't have a new model; or do backport. >> > > > > >> > > > >Plus, DPDK is now dependent...
2018 Apr 23
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, 23 Apr 2018 20:24:56 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Mon, Apr 23, 2018 at 10:04:06AM -0700, Stephen Hemminger wrote: > > > > > > > >I will NAK patches to change to common code for netvsc especially the > > > >three device model. MS worked hard with distro vendors to support transparent > > > >mode, ans we really can't have a new model; or do backport. > > > > > > > >Plus, DPDK is now dependent on existing model. > > &gt...
2018 Apr 23
2
[PATCH v7 net-next 4/4] netvsc: refactor notifier/event handling code to use the failover framework
On Mon, 23 Apr 2018 20:24:56 +0300 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Mon, Apr 23, 2018 at 10:04:06AM -0700, Stephen Hemminger wrote: > > > > > > > >I will NAK patches to change to common code for netvsc especially the > > > >three device model. MS worked hard with distro vendors to support transparent > > > >mode, ans we really can't have a new model; or do backport. > > > > > > > >Plus, DPDK is now dependent on existing model. > > &gt...
2011 Feb 14
2
[PATCH 1/2] staging: hv: Remove dead code from netvsc.c
Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> --- drivers/staging/hv/netvsc.c | 34 ---------------------------------- 1 files changed, 0 insertions(+), 34 deletions(-) diff --git a/drivers/staging/hv/netvsc.c b/drivers/staging/hv/netvsc.c index fa46a7e..8c6d4ae 100644 --- a/drivers/staging/hv/netvsc.c +++ b/drivers...