Best regard, ZHANG Jialiang
> 在 2016年9月29日，03:00，discuss-request <discuss-requ...@openvswitch.org> 写道： > > Send discuss mailing list submissions to > discuss@openvswitch.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://openvswitch.org/mailman/listinfo/discuss > or, via email, send a message with subject or body 'help' to > discuss-requ...@openvswitch.org > > You can reach the person managing the list at > discuss-ow...@openvswitch.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of discuss digest..." > > > Today's Topics: > > 1. Re: Open vSwitch 2.6.0 and 2.5.1 Available (Markos Chandras) > 2. Router setup output:LOCAL problem (Tugrul Erdogan) > 3. Re: Open vSwitch 2.6.0 and 2.5.1 Available (Ben Pfaff) > 4. OVS 2.5 crashes when setting n-dpdk-rxqs to 64 w/ two dpdk > ports. (Wojciechowicz, RobertX) > 5. OVS 2.6.90 & ODL Beryllium (Richard Renwick) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 28 Sep 2016 11:36:01 +0100 > From: Markos Chandras <mchand...@suse.de> > To: discuss@openvswitch.org > Subject: Re: [ovs-discuss] Open vSwitch 2.6.0 and 2.5.1 Available > Message-ID: <ee3ca92f-9065-1643-679b-21b7e4e7b...@suse.de> > Content-Type: text/plain; charset=utf-8 > >> On 09/28/2016 08:01 AM, Justin Pettit wrote: >> The Open vSwitch team is pleased to announce the release of Open vSwitch >> 2.6.0: >> [...] >> In addition to the 2.6.0 release, we've also released 2.5.1: >> >> http://openvswitch.org/releases/openvswitch-2.5.1.tar.gz >> > > Hi, > > I can't see the new 2 release tags on github. Any chance you can push them? > > -- > markos > > SUSE LINUX GmbH | GF: Felix Imendörffer, Jane Smithard, Graham Norton > HRB 21284 (AG Nürnberg) Maxfeldstr. 5, D-90409, Nürnberg > > > ------------------------------ > > Message: 2 > Date: Wed, 28 Sep 2016 15:44:15 +0300 > From: Tugrul Erdogan <h.tugrul.erdo...@gmail.com> > To: discuss@openvswitch.org > Subject: [ovs-discuss] Router setup output:LOCAL problem > Message-ID: > <CA+whn7Qf3-vNuX5+vUwRA-5NMNpiRJVpBzdFfULjzgL1b=4...@mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > Hi all, > > I am working on routing packages by operation system routing mechanism > on openvswitch bridges (10.4.4.5 -> 10.3.4.6). My topology contains > two ovs bridge (external and internal bridge) and between that ovs > bridges a namespace which has two ovs bridge ports. I want to route > packages which are comes from external ovs bridge to ovs internal > bridge ( the path contains namespace external and internal ports too). > > I can see that the packeges comes ovs-brint and matches with > "output:LOCAL" flow rule but I can not nor see that packages at > operation system neighter see the "in_port=LOCAL" flow rule matches. > What can be the problem? > > The configuration below (I try to output the packages to LOCAL to > operation system routing processing at ovs-brext and after that > routing processing re-direct same package to output port on > ovs-brext): > > > [~]# ovs-ofctl show ovs-brext > OFPT_FEATURES_REPLY (xid=0x2): dpid:000000900b2410ca > n_tables:254, n_buffers:256 > capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP > actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan > mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src > mod_tp_dst > 1(v-peer2): addr:00:00:00:00:00:00 > config: PORT_DOWN > state: LINK_DOWN > speed: 0 Mbps now, 0 Mbps max > 2(v-peer1): addr:00:00:00:00:00:00 > config: PORT_DOWN > state: LINK_DOWN > speed: 0 Mbps now, 0 Mbps max > 3(enp9s0f0): addr:00:90:0b:24:10:ca > config: 0 > state: 0 > current: 10GB-FD FIBER > advertised: 10GB-FD FIBER > supported: 10GB-FD FIBER > speed: 10000 Mbps now, 10000 Mbps max > LOCAL(ovs-brext): addr:00:90:0b:24:10:ca > config: 0 > state: 0 > speed: 0 Mbps now, 0 Mbps max > OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 > > > > [~]# ovs-ofctl show ovs-brint > OFPT_FEATURES_REPLY (xid=0x2): dpid:000000900b2410cb > n_tables:254, n_buffers:256 > capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP > actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan > mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src > mod_tp_dst > 1(rv-peer2): addr:00:00:00:00:00:00 > config: PORT_DOWN > state: LINK_DOWN > speed: 0 Mbps now, 0 Mbps max > 2(rv-peer1): addr:00:00:00:00:00:00 > config: PORT_DOWN > state: LINK_DOWN > speed: 0 Mbps now, 0 Mbps max > 3(enp9s0f1): addr:00:90:0b:24:10:cb > config: 0 > state: 0 > current: 10GB-FD FIBER > advertised: 10GB-FD FIBER > supported: 10GB-FD FIBER > speed: 10000 Mbps now, 10000 Mbps max > LOCAL(ovs-brint): addr:00:90:0b:24:10:cb > config: 0 > state: 0 > speed: 0 Mbps now, 0 Mbps max > OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 > > > > [~]# ovs-ofctl dump-flows ovs-brext > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=260.230s, table=0, n_packets=260, n_bytes=25480, > idle_age=0, ip,in_port=3,nw_dst=10.3.4.6 actions=output:2 > cookie=0x0, duration=82763.504s, table=0, n_packets=437774868, > n_bytes=26267249426, idle_age=7, hard_age=65534, priority=0 > actions=NORMAL > > > [~]# ovs-ofctl dump-flows ovs-brint > NXST_FLOW reply (xid=0x4): > cookie=0x0, duration=241.808s, table=0, n_packets=242, n_bytes=23716, > idle_age=0, ip,in_port=2,nw_dst=10.3.4.6 actions=LOCAL > cookie=0x0, duration=235.897s, table=0, n_packets=0, n_bytes=0, > idle_age=235, ip,in_port=LOCAL,nw_dst=10.3.4.6 actions=output:3 > cookie=0x0, duration=82761.087s, table=0, n_packets=126281614, > n_bytes=7577057394, idle_age=242, hard_age=65534, priority=0 > actions=NORMAL > > > > Thanks for your helps, > Best regards, > Tugrul > > > ------------------------------ > > Message: 3 > Date: Wed, 28 Sep 2016 08:27:24 -0700 > From: Ben Pfaff <b...@ovn.org> > To: Markos Chandras <mchand...@suse.de> > Cc: discuss@openvswitch.org > Subject: Re: [ovs-discuss] Open vSwitch 2.6.0 and 2.5.1 Available > Message-ID: <20160928152724.go12...@ovn.org> > Content-Type: text/plain; charset=us-ascii > >> On Wed, Sep 28, 2016 at 11:36:01AM +0100, Markos Chandras wrote: >>> On 09/28/2016 08:01 AM, Justin Pettit wrote: >>> The Open vSwitch team is pleased to announce the release of Open vSwitch >>> 2.6.0: >>> [...] >>> In addition to the 2.6.0 release, we've also released 2.5.1: >>> >>> http://openvswitch.org/releases/openvswitch-2.5.1.tar.gz >>> >> >> Hi, >> >> I can't see the new 2 release tags on github. Any chance you can push them? > > Done now. > > > ------------------------------ > > Message: 4 > Date: Wed, 28 Sep 2016 09:57:50 +0000 > From: "Wojciechowicz, RobertX" <robertx.wojciechow...@intel.com> > To: "john.philli...@hpe.com" <john.philli...@hpe.com> > Cc: "discuss@openvswitch.org" <discuss@openvswitch.org> > Subject: [ovs-discuss] OVS 2.5 crashes when setting n-dpdk-rxqs to 64 > w/ two dpdk ports. > Message-ID: > <ed71ee0c15b44e41b8fa814d7efd5ca8c44...@irsmsx103.ger.corp.intel.com> > Content-Type: text/plain; charset="us-ascii" > >> On Fri, Sep 16, 2016 at 05:11:11PM +0000, John Phillips wrote: >> When I try to set other_config:n-dpdk-rxqs to 64 with two intel niantic dpdk >> ports on a single dpdk bridge, the bridge instance will 'crash' - I >> can't access >> it's flows through ovs-ofctl commands. I am running an OVS from the 2.5 >> branch, >> specifically commit ID b3e263929a7a00c96a1329f93f1b8fce58b726e4, DPDK 16.04. >> > > I investigated this issue using these software versions: > OVS: master (commit: 05bb914854831f58c61343570d8b10d6059646b8) > DPDK: v16.07 > > It seems that this problem is related to the static memory pool allocation > with hardcoded size. > > In OVS in netdev_dpdk.c: dpdk_mp_get function there is following comment: > """ > /* XXX: this is a really rough method of provisioning memory. > It's impossible to determine what the exact memory requirements are when > the number of ports and rxqs that utilize a particular mempool can change > dynamically at runtime. For the moment, use this rough heurisitic. > */ > """ > and it seems that for this case there is just not enough memory allocated. > > By default OVS allocates memory pool for 128 queues (default queue size: 2048) > as follows: > #define MAX_NB_MBUF (4096 * 64) > > If memory pool is exhausted then following error appears: > > """ > PMD: ixgbe_alloc_rx_queue_mbufs(): RX mbuf alloc failed queue_id=62 > PMD: ixgbe_dev_rx_queue_start(): Could not alloc mbuf for queue:62 > PMD: ixgbe_dev_start(): Unable to start rxtx queues > PMD: ixgbe_dev_start(): failure in ixgbe_dev_start(): -1 > """ > > So my proposal to solve this problem is making the value MAX_NB_MBUF > (maximum memory pool size) configurable in OVS DB. > In my tests increasing this value to (4096 * 66) allowed for creation two > ports > with 64 rx queues each. > > Please let me know if such configuration might be useful for you, > so it makes sense to start working on the OVS patch. > > Br, > Robert > > > > > > > ------------------------------ > > Message: 5 > Date: Wed, 28 Sep 2016 14:42:48 +0100 > From: Richard Renwick <richard.renw...@yahoo.com> > To: discuss@openvswitch.org > Subject: [ovs-discuss] OVS 2.6.90 & ODL Beryllium > Message-ID: <60748ddd-8fdb-4d49-b637-55b8ec1bf...@yahoo.com> > Content-Type: text/plain; charset=utf-8 > > Hi all, > Over the last few days I have been experimenting with NAT in OVS. I have > successfully set up the flows I need using ovs-vsctl but now I want to do it > using the northbound interface of ODL (Beryllium). However, I am really > struggling to get to grips with how to implement the “ct” & “nat” actions in > my ovs-vsctl commands. I have pasted just one of the OVS commands below as > an example: > > ovs-ofctl add-flow br0 > table=1,priority=200,in_port=2,actions=ct(commit,zone=10,nat(dst=1.1.1.1)),3 > > I am not sure if a YANG model needs to be updated in ODL. If so, then I have > no clue on how to do that. If I am barking up the wrong tree then any help > would be appreciated. As you will be able to tell, I am new to playing with > ODL & OVS. > > Thanks for any ideas or help. > > Cheers, > Rich > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss > > > ------------------------------ > > End of discuss Digest, Vol 87, Issue 65 > *************************************** _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
