[ovs-dev] (no subject)
___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
[ovs-dev] (no subject)
The original message was received at Sun, 15 Mar 2015 22:56:25 +0700 from openvswitch.org [27.238.118.10] - The following addresses had permanent fatal errors - - Transcript of session follows - ... while talking to mail server 68.124.15.88: >>> DATA <<< 400-aturner; -SYSTEM-F-EXDISKQUOTA, disk quota exceeded <<< 400 ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] [PATCH v2 2/3] datapath-windows: Support for multiple VXLAN tunnels
hi Sorin,
This change looks good.
Have you tested the scenario of unloading the OVS extension while the VXLAN
ports exist in the kernel?
I had a minor comment as follows, but looks good otherwise.
> static __inline BOOLEAN
> OvsIsInternalVportType(OVS_VPORT_TYPE ovsType)
> {
> diff --git a/datapath-windows/ovsext/Vxlan.c b/datapath-windows/ovsext/Vxlan.c
> index cd3dc45..a22c425 100644
> --- a/datapath-windows/ovsext/Vxlan.c
> +++ b/datapath-windows/ovsext/Vxlan.c
> @@ -259,7 +259,7 @@ OvsDoEncapVxlan(PNET_BUFFER_LIST curNbl,
> /* UDP header */
> udpHdr = (UDPHdr *)((PCHAR)ipHdr + sizeof *ipHdr);
> udpHdr->source = htons(tunKey->flow_hash | 32768);
> -udpHdr->dest = VXLAN_UDP_PORT_NBO;
> +udpHdr->dest = htons(tunKey->dst_port);
Tunnel key is generally in Network order already. Why do we need to convert it?
Acked-by: Nithin Raju
-- Nithin
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] [PATCH 3/3] netlink: support for asynchronous NL transactions
> On Mar 12, 2015, at 5:42 PM, Sorin Vinturis > wrote: > > Modified 'nl_sock_transact_multiple__' function to send asynchronous > I/O requests to the kernel driver. > > Signed-off-by: Sorin Vinturis > Reported-by: Alin Gabriel Serdean > Reported-at: > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs-2Dissues_issues_64&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=pNHQcdr7B40b4h6Yb7FIedI1dnBsxdDuTLBYD3JqV80&m=ptyT-4_KX9K220F3nw2WYFTDxbFegQddmHarVmB6PKc&s=__1QDaT8DB13yENZfteePG67ZSDCflB3F6hDW29RCjY&e= > > --- > lib/netlink-socket.c | 26 ++ > 1 file changed, 22 insertions(+), 4 deletions(-) Hypothetically, if the kernel does not complete the IRP, then one or more of the userspace threads is stuck on GetOverlappedResult(). If you Ctrl-C the ovs-vswitchd process at that point, what happens to the pending IRP? Does it get cleaned up as part of process exit, or will we get a PSOD? thanks, -- Nithin ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
[ovs-dev] A surprising letter From America's richest philanthropists
Congratulations, This email correspondence is from Bill and Melinda Gates, America's richest philanthropists. Your email is among the thirteen(13) emails that have just been randomly selected by a Microsoft� 1E� powered email Newsletter software operated by legally registered British, American and EU freelance tech experts upon our request to receive a financial support donation of $2million each, from my wife and I as part of our annual efforts aimed at reducing income inequality gap around the world. My wife and I have provided more than $30.2 billion in funding toward research and innovation in science, education, health, and technology and believes that breakthroughs in these areas will make a dramatic impact globally in the years to come. Ranked as the most philanthropic couple across the country, my wife and I donated $2.65 billion last year toward fighting diseases and reforming education, scientific research, financial empowerment programmes, among other initiatives. My wife and I coordinate our efforts through the Bill and Melinda Gates Foundation, which works with other people to donate money and resources on trying to solve a select number of global problems and concerns. I understand that you might feel skeptical, considering the fact that this seems quite unbelievable, however, Please see links below so as to gain an insight into what we ve done so far over the years; http://www.dailymotion.com/video/x1oggua_bill-and-melinda-gates-why-giving-away-our-wealth-has-been-the-most-satisfying-thing-we-ve-done_lifestyle http://news.yahoo.com/katie-couric-interviews-bill-and-melinda-gates-040753364.html ; http://www.bbc.com/news/entertainment-arts-11565953 You may get back to us here with any accepted means of identification or Full Names, Telephone/Phone, Age, and Country of Residence. Bill & Melinda Gates. ©2015 Bill & Melinda Gates Annual Email Financial Donation Project. ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
[ovs-dev] OVS Windows MSI installer
Hi guys, As discussed on IRC, here's the Windows MSI installer project that we’d like to submit for upstream inclusion: https://github.com/cloudbase/ovs-windows-installer The included README.rst provides information on how to generate the MSI and I’ll also be happy to answer any question and review. In terms of location of the code, we could IMO either include the installer as a separate project on https://github.com/openvswitch or as a subfolder under the https://github.com/openvswitch/ovs project itself. My vote is for the first option, but if you guys prefer the second I’ll be happy to send the full patchset on the ML for review. Thanks, Alessandro ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] OVS Windows MSI installer
On Mon, Mar 16, 2015 at 12:33:09AM +, Alessandro Pilotti wrote: > As discussed on IRC, here's the Windows MSI installer project that we’d like > to > submit for upstream inclusion: > > https://github.com/cloudbase/ovs-windows-installer > > The included README.rst provides information on how to generate the MSI and > I’ll also be happy to answer any question and review. > > In terms of location of the code, we could IMO either include the installer as > a separate project on https://github.com/openvswitch or as a subfolder under > the https://github.com/openvswitch/ovs project itself. > My vote is for the first option, but if you guys prefer the second I’ll be > happy to send the full patchset on the ML for review. Thanks for writing this and publishing it! One factor in deciding whether this should be part of the OVS tree or part of a separate tree is how closely coupled it is with the rest of the OVS tree. If it's likely that changes to OVS (new files or whatever) would require changes in the installer, then that makes me tend to believe that the installer should be part of the OVS tree, because then it becomes possible to fix up the installer in the same commit that changes OVS. That is one reason that it is nice to have, for example, the Debian and Red Hat packaging in the OVS tree. What are your thoughts on that issue? (I have not looked at the installer tree.) Thanks, Ben. ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] OVS Windows MSI installer
Hi Alessandro, I couldn't find the driver binary as part of the installer. Also, can you explain how uninstlaation is done and the case where a driver is already loaded. Thank you! Eitan -Original Message- From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Alessandro Pilotti Sent: Sunday, March 15, 2015 5:33 PM To: dev@openvswitch.org Subject: [ovs-dev] OVS Windows MSI installer Hi guys, As discussed on IRC, here's the Windows MSI installer project that we’d like to submit for upstream inclusion: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=ssYlF73rox7Qc5jV0EuVGd31T3gjOjJrGilWxhpfCQU&e= The included README.rst provides information on how to generate the MSI and I’ll also be happy to answer any question and review. In terms of location of the code, we could IMO either include the installer as a separate project on https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=j7vZQ7TETCqJcuj8GlWvxlDQj3eaZDowoeugOoF62m4&e= or as a subfolder under the https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=64IUwcJqsI-IqUHcDpffloCd02L8ksBeDjCy2OB09So&e= project itself. My vote is for the first option, but if you guys prefer the second I’ll be happy to send the full patchset on the ML for review. Thanks, Alessandro ___ dev mailing list dev@openvswitch.org https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=Q9DuaqvXtQI-5E0ozVMau9cLqIUtEVFPGxNzhW5FhtU&e= ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] OVS Windows MSI installer
> On 16 Mar 2015, at 02:41, Ben Pfaff wrote: > > On Mon, Mar 16, 2015 at 12:33:09AM +, Alessandro Pilotti wrote: >> As discussed on IRC, here's the Windows MSI installer project that we’d like >> to >> submit for upstream inclusion: >> >> https://github.com/cloudbase/ovs-windows-installer >> >> The included README.rst provides information on how to generate the MSI and >> I’ll also be happy to answer any question and review. >> >> In terms of location of the code, we could IMO either include the installer >> as >> a separate project on https://github.com/openvswitch or as a subfolder under >> the https://github.com/openvswitch/ovs project itself. >> My vote is for the first option, but if you guys prefer the second I’ll be >> happy to send the full patchset on the ML for review. > > Thanks for writing this and publishing it! > > One factor in deciding whether this should be part of the OVS tree or > part of a separate tree is how closely coupled it is with the rest of > the OVS tree. If it's likely that changes to OVS (new files or > whatever) would require changes in the installer, then that makes me > tend to believe that the installer should be part of the OVS tree, > because then it becomes possible to fix up the installer in the same > commit that changes OVS. That is one reason that it is nice to have, > for example, the Debian and Red Hat packaging in the OVS tree. What are > your thoughts on that issue? (I have not looked at the installer tree.) > > Thanks, > > Ben. We kept the coupling between the installer and the OVS projects as loose as possible. For example the installer build makes no assumptions on the content of the CLI binaries folder (ovs-vsctl.exe, etc), it just takes whatever the OVS build process generated and includes the binaries in the installer. The only real coupling is in the fact that we expect to have one kernel driver and two Windows services (daemons): ovs-vswitchd and ovsdb-server. This means that changes to the project are required in case a new daemon or driver is going to be added, but I expect this to be a very rare scenario. Alessandro ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] OVS Windows MSI installer
Hi Eitan, > On 16 Mar 2015, at 02:57, Eitan Eliahu wrote: > > > Hi Alessandro, > I couldn't find the driver binary as part of the installer. Also, can you > explain how uninstlaation is done and the case where a driver is already > loaded. As explained in the README, the actual binaries are produced by the OVS build, so it does not make sense to include them in this project, otherwise we’d need to commit the binaries at every OVS build. During uninstall the driver is removed. The general rule for Windows installers is that whatever gets installed, must be removed on uninstall (except user generated content, e.g. configuration files). I didn’t include the WMI / PowerShell call for deregistering the extension from Hyper-V switches yet, since infamously that operation generated a significant amount of crashes until very recently (we still have a pending patch on this topic AFAIK). Here is where the driver is uninstalled: https://github.com/cloudbase/ovs-windows-installer/blob/master/ovs-windows-installer/Product.wxs#L48-L49 Alessandro > Thank you! > Eitan > > -Original Message- > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Alessandro Pilotti > Sent: Sunday, March 15, 2015 5:33 PM > To: dev@openvswitch.org > Subject: [ovs-dev] OVS Windows MSI installer > > Hi guys, > > > > As discussed on IRC, here's the Windows MSI installer project that we’d like > to > > submit for upstream inclusion: > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=ssYlF73rox7Qc5jV0EuVGd31T3gjOjJrGilWxhpfCQU&e= > > > > > The included README.rst provides information on how to generate the MSI and > > I’ll also be happy to answer any question and review. > > > > In terms of location of the code, we could IMO either include the installer as > > a separate project on > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=j7vZQ7TETCqJcuj8GlWvxlDQj3eaZDowoeugOoF62m4&e= > or as a subfolder under > > the > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=64IUwcJqsI-IqUHcDpffloCd02L8ksBeDjCy2OB09So&e= > project itself. > > My vote is for the first option, but if you guys prefer the second I’ll be > > happy to send the full patchset on the ML for review. > > > > Thanks, > > > > Alessandro > > > > ___ > dev mailing list > dev@openvswitch.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=Q9DuaqvXtQI-5E0ozVMau9cLqIUtEVFPGxNzhW5FhtU&e= > ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] OVS Windows MSI installer
Alessandro, Yes, no problem of having the installer separate. But, I am confused as I see the two services are there but the driver and the INF file are not. I believe that the MSI file includes everything. Do you think you can add the OS installer script? Will we have already built MSI file (x86 and x86-64)? Thanks, Eitan -Original Message- From: Alessandro Pilotti [mailto:apilo...@cloudbasesolutions.com] Sent: Sunday, March 15, 2015 6:11 PM To: Eitan Eliahu Cc: dev@openvswitch.org Subject: Re: OVS Windows MSI installer Hi Eitan, > On 16 Mar 2015, at 02:57, Eitan Eliahu wrote: > > > Hi Alessandro, > I couldn't find the driver binary as part of the installer. Also, can you > explain how uninstlaation is done and the case where a driver is already > loaded. As explained in the README, the actual binaries are produced by the OVS build, so it does not make sense to include them in this project, otherwise we’d need to commit the binaries at every OVS build. During uninstall the driver is removed. The general rule for Windows installers is that whatever gets installed, must be removed on uninstall (except user generated content, e.g. configuration files). I didn’t include the WMI / PowerShell call for deregistering the extension from Hyper-V switches yet, since infamously that operation generated a significant amount of crashes until very recently (we still have a pending patch on this topic AFAIK). Here is where the driver is uninstalled: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller_blob_master_ovs-2Dwindows-2Dinstaller_Product.wxs-23L48-2DL49&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=WmmTcAbYsoZf0kKnbhjcKx6VU2dw-WDIcSF-V8Gtd94&s=ksjvS04wlV-fvUUTh7wLch51SUmIkKEpjAxRNZtebAw&e= Alessandro > Thank you! > Eitan > > -Original Message- > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Alessandro Pilotti > Sent: Sunday, March 15, 2015 5:33 PM > To: dev@openvswitch.org > Subject: [ovs-dev] OVS Windows MSI installer > > Hi guys, > > > > As discussed on IRC, here's the Windows MSI installer project that we’d like > to > > submit for upstream inclusion: > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=ssYlF73rox7Qc5jV0EuVGd31T3gjOjJrGilWxhpfCQU&e= > > > > > The included README.rst provides information on how to generate the MSI and > > I’ll also be happy to answer any question and review. > > > > In terms of location of the code, we could IMO either include the installer as > > a separate project on > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=j7vZQ7TETCqJcuj8GlWvxlDQj3eaZDowoeugOoF62m4&e= > or as a subfolder under > > the > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=64IUwcJqsI-IqUHcDpffloCd02L8ksBeDjCy2OB09So&e= > project itself. > > My vote is for the first option, but if you guys prefer the second I’ll be > > happy to send the full patchset on the ML for review. > > > > Thanks, > > > > Alessandro > > > > ___ > dev mailing list > dev@openvswitch.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=Q9DuaqvXtQI-5E0ozVMau9cLqIUtEVFPGxNzhW5FhtU&e= > ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] OVS Windows MSI installer
Alessandro, How the MSI solution find files from the OVS build that need to be included? Thanks, Eitan -Original Message- From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Eitan Eliahu Sent: Sunday, March 15, 2015 6:30 PM To: Alessandro Pilotti Cc: dev@openvswitch.org Subject: Re: [ovs-dev] OVS Windows MSI installer Alessandro, Yes, no problem of having the installer separate. But, I am confused as I see the two services are there but the driver and the INF file are not. I believe that the MSI file includes everything. Do you think you can add the OS installer script? Will we have already built MSI file (x86 and x86-64)? Thanks, Eitan -Original Message- From: Alessandro Pilotti [mailto:apilo...@cloudbasesolutions.com] Sent: Sunday, March 15, 2015 6:11 PM To: Eitan Eliahu Cc: dev@openvswitch.org Subject: Re: OVS Windows MSI installer Hi Eitan, > On 16 Mar 2015, at 02:57, Eitan Eliahu wrote: > > > Hi Alessandro, > I couldn't find the driver binary as part of the installer. Also, can you > explain how uninstlaation is done and the case where a driver is already > loaded. As explained in the README, the actual binaries are produced by the OVS build, so it does not make sense to include them in this project, otherwise we’d need to commit the binaries at every OVS build. During uninstall the driver is removed. The general rule for Windows installers is that whatever gets installed, must be removed on uninstall (except user generated content, e.g. configuration files). I didn’t include the WMI / PowerShell call for deregistering the extension from Hyper-V switches yet, since infamously that operation generated a significant amount of crashes until very recently (we still have a pending patch on this topic AFAIK). Here is where the driver is uninstalled: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller_blob_master_ovs-2Dwindows-2Dinstaller_Product.wxs-23L48-2DL49&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=WmmTcAbYsoZf0kKnbhjcKx6VU2dw-WDIcSF-V8Gtd94&s=ksjvS04wlV-fvUUTh7wLch51SUmIkKEpjAxRNZtebAw&e= Alessandro > Thank you! > Eitan > > -Original Message- > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Alessandro Pilotti > Sent: Sunday, March 15, 2015 5:33 PM > To: dev@openvswitch.org > Subject: [ovs-dev] OVS Windows MSI installer > > Hi guys, > > > > As discussed on IRC, here's the Windows MSI installer project that we’d like > to > > submit for upstream inclusion: > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=ssYlF73rox7Qc5jV0EuVGd31T3gjOjJrGilWxhpfCQU&e= > > > > > The included README.rst provides information on how to generate the MSI and > > I’ll also be happy to answer any question and review. > > > > In terms of location of the code, we could IMO either include the installer as > > a separate project on > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=j7vZQ7TETCqJcuj8GlWvxlDQj3eaZDowoeugOoF62m4&e= > or as a subfolder under > > the > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=64IUwcJqsI-IqUHcDpffloCd02L8ksBeDjCy2OB09So&e= > project itself. > > My vote is for the first option, but if you guys prefer the second I’ll be > > happy to send the full patchset on the ML for review. > > > > Thanks, > > > > Alessandro > > > > ___ > dev mailing list > dev@openvswitch.org > https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=Q9DuaqvXtQI-5E0ozVMau9cLqIUtEVFPGxNzhW5FhtU&e= > ___ dev mailing list dev@openvswitch.org https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=E8G40dNCxrZ38oxXQmMUMaHyuhmF76rDGyoDLu_wGKE&s=ia3tRWFMlcRaiMrcYWBFlaohQfmUS0l1hHhy7z_lNSo&e= __
Re: [ovs-dev] [PATCH v8] netdev-dpdk: add dpdk vhost-cuse ports
On Thu, Mar 12, 2015 at 7:18 AM, Traynor, Kevin wrote: > >> -Original Message- >> From: Pravin Shelar [mailto:pshe...@nicira.com] >> Sent: Thursday, March 12, 2015 7:20 AM >> To: Traynor, Kevin >> Cc: dev@openvswitch.org >> Subject: Re: [ovs-dev] [PATCH v8] netdev-dpdk: add dpdk vhost-cuse ports >> >> On Thu, Mar 5, 2015 at 1:42 PM, Kevin Traynor >> wrote: >> > This patch adds support for a new port type to userspace datapath >> > called dpdkvhost. This allows KVM (QEMU) to offload the servicing >> > of virtio-net devices to its associated dpdkvhost port. Instructions >> > for use are in INSTALL.DPDK. >> > >> > This has been tested on Intel multi-core platforms and with clients >> > that have virtio-net interfaces. >> > >> >> What is required QEMU version for this patch ? > > It's been tested with 2.1.0 and 2.2.0. It has also previously been tested > with 1.6.2 but only the '-mem-path /dev/hugepages -mem-prealloc' flags are > needed to share the hugepage for that version. It won't work with 2.0.0 as > there isn't a way to share the hugepage. > Thanks for the info. I will try it this week. I had another question about netdev-dpdk mutex, why is it converted to spin_lock? ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
Re: [ovs-dev] OVS Windows MSI installer
Eitan, The general process is: 1) build OVS project 2) copy generated binaries in the locations expected as explained in the README 3) build installer project We have scripts that do that end other steps like code signing as part the the continuos build system, but it's really that simple. > On 16 mar. 2015, at 03:49, Eitan Eliahu wrote: > > Alessandro, How the MSI solution find files from the OVS build that need to > be included? > Thanks, > Eitan > > > -Original Message- > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Eitan Eliahu > Sent: Sunday, March 15, 2015 6:30 PM > To: Alessandro Pilotti > Cc: dev@openvswitch.org > Subject: Re: [ovs-dev] OVS Windows MSI installer > > > > Alessandro, > > Yes, no problem of having the installer separate. But, I am confused as I > see the two services are there but the driver and the INF file are not. I > believe that the MSI file includes everything. > > Do you think you can add the OS installer script? > > Will we have already built MSI file (x86 and x86-64)? > > Thanks, > > Eitan > > > > -Original Message- > > From: Alessandro Pilotti [mailto:apilo...@cloudbasesolutions.com] > > Sent: Sunday, March 15, 2015 6:11 PM > > To: Eitan Eliahu > > Cc: dev@openvswitch.org > > Subject: Re: OVS Windows MSI installer > > > > Hi Eitan, > > > > > > > >> On 16 Mar 2015, at 02:57, Eitan Eliahu wrote: > > > > > > > > > >> Hi Alessandro, > > > >> I couldn't find the driver binary as part of the installer. Also, can you >> explain how uninstlaation is done and the case where a driver is already >> loaded. > > > > > > > > As explained in the README, the actual binaries are produced by the OVS > build, so it does not make sense to include them in this project, otherwise > we’d need to commit the binaries at every OVS build. > > > > > > > > During uninstall the driver is removed. The general rule for Windows > installers is that whatever gets installed, must be removed on uninstall > (except user generated content, e.g. configuration files). > > > > I didn’t include the WMI / PowerShell call for deregistering the extension > from Hyper-V switches yet, since infamously that operation generated a > significant amount of crashes until very recently (we still have a pending > patch on this topic AFAIK). > > > > > > > > Here is where the driver is uninstalled: > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller_blob_master_ovs-2Dwindows-2Dinstaller_Product.wxs-23L48-2DL49&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=WmmTcAbYsoZf0kKnbhjcKx6VU2dw-WDIcSF-V8Gtd94&s=ksjvS04wlV-fvUUTh7wLch51SUmIkKEpjAxRNZtebAw&e= > > > > > > > > > > > > > Alessandro > > > > > > > > > > > >> Thank you! > > > >> Eitan > > > > > > >> -Original Message- > > > >> From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Alessandro >> Pilotti > > > >> Sent: Sunday, March 15, 2015 5:33 PM > > > >> To: dev@openvswitch.org > > > >> Subject: [ovs-dev] OVS Windows MSI installer > > > > > > >> Hi guys, > > > > > > > > > > > > >> As discussed on IRC, here's the Windows MSI installer project that we’d like >> to > > > > > > >> submit for upstream inclusion: > > > > > > > > > > > > >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=ssYlF73rox7Qc5jV0EuVGd31T3gjOjJrGilWxhpfCQU&e= > > > > > > > > > > > > >> The included README.rst provides information on how to generate the MSI and > > > > > > >> I’ll also be happy to answer any question and review. > > > > > > > > > > > > >> In terms of location of the code, we could IMO either include the installer >> as > > > > > > >> a separate project on >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=j7vZQ7TETCqJcuj8GlWvxlDQj3eaZDowoeugOoF62m4&e= >> or as a subfolder under > > > > > > >> the >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=64IUwcJqsI-IqUHcDpffloCd02L8ksBeDjCy2OB09So&e= >> project itself. > > > > > > >> My vote is for the first option, but if you guys prefer the second I’ll be > > > > > > >> happy to send the full patchset on the ML for review. > > > > > > > > > > > > >> Thanks, > > > > > > > > > > > > >> Alessandro >
Re: [ovs-dev] OVS Windows MSI installer
> On 16 mar. 2015, at 03:30, Eitan Eliahu wrote: > > > Alessandro, > Yes, no problem of having the installer separate. But, I am confused as I > see the two services are there but the driver and the INF file are not. I > believe that the MSI file includes everything. > Do you think you can add the OS installer script? > Will we have already built MSI file (x86 and x86-64)? We'll commit the x64 MSI build code as soon as we have the x64 OVS build merged upstream. One thing that we should decide is if it makes sense to keep a separate x86 build at all at that point. Since Hyper-V is limited to x64, the only use case for a x86 build is for a 32bit client OS build where a user wants to install the CLI tools only. Given how limited this use case is, I'd go with a single x64 build. > Thanks, > Eitan > > -Original Message- > From: Alessandro Pilotti [mailto:apilo...@cloudbasesolutions.com] > Sent: Sunday, March 15, 2015 6:11 PM > To: Eitan Eliahu > Cc: dev@openvswitch.org > Subject: Re: OVS Windows MSI installer > > Hi Eitan, > > > >>> On 16 Mar 2015, at 02:57, Eitan Eliahu wrote: >> > > >> Hi Alessandro, > >> I couldn't find the driver binary as part of the installer. Also, can you >> explain how uninstlaation is done and the case where a driver is already >> loaded. > > > > As explained in the README, the actual binaries are produced by the OVS > build, so it does not make sense to include them in this project, otherwise > we’d need to commit the binaries at every OVS build. > > > > During uninstall the driver is removed. The general rule for Windows > installers is that whatever gets installed, must be removed on uninstall > (except user generated content, e.g. configuration files). > > I didn’t include the WMI / PowerShell call for deregistering the extension > from Hyper-V switches yet, since infamously that operation generated a > significant amount of crashes until very recently (we still have a pending > patch on this topic AFAIK). > > > > Here is where the driver is uninstalled: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller_blob_master_ovs-2Dwindows-2Dinstaller_Product.wxs-23L48-2DL49&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=WmmTcAbYsoZf0kKnbhjcKx6VU2dw-WDIcSF-V8Gtd94&s=ksjvS04wlV-fvUUTh7wLch51SUmIkKEpjAxRNZtebAw&e= > > > > > > > Alessandro > > > > > >> Thank you! > >> Eitan > > >> -Original Message- > >> From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Alessandro >> Pilotti > >> Sent: Sunday, March 15, 2015 5:33 PM > >> To: dev@openvswitch.org > >> Subject: [ovs-dev] OVS Windows MSI installer > > >> Hi guys, > > > > >> As discussed on IRC, here's the Windows MSI installer project that we’d like >> to > > >> submit for upstream inclusion: > > > > >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_cloudbase_ovs-2Dwindows-2Dinstaller&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=ssYlF73rox7Qc5jV0EuVGd31T3gjOjJrGilWxhpfCQU&e= > > > > >> The included README.rst provides information on how to generate the MSI and > > >> I’ll also be happy to answer any question and review. > > > > >> In terms of location of the code, we could IMO either include the installer >> as > > >> a separate project on >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=j7vZQ7TETCqJcuj8GlWvxlDQj3eaZDowoeugOoF62m4&e= >> or as a subfolder under > > >> the >> https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openvswitch_ovs&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=64IUwcJqsI-IqUHcDpffloCd02L8ksBeDjCy2OB09So&e= >> project itself. > > >> My vote is for the first option, but if you guys prefer the second I’ll be > > >> happy to send the full patchset on the ML for review. > > > > >> Thanks, > > > > >> Alessandro > > > > >> ___ > >> dev mailing list > >> dev@openvswitch.org > >> https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_mailman_listinfo_dev&d=AwIGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=CWsgHUxi6ExLXY798tmo3LJ4e3geGYp56lkcH-5cLCY&m=utkZq_G_Z0gpFYbAClV8e6AD4sXWL1oC5IbDSJwm-Dk&s=Q9DuaqvXtQI-5E0ozVMau9cLqIUtEVFPGxNzhW5FhtU&e= > > > ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
