summaryrefslogtreecommitdiffstats
path: root/docs/submodules/samplevnf
AgeCommit message (Collapse)AuthorFilesLines
2018-08-14Update git submodulesPatrice Buriez1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Fix potential crash with latency accuracy Detect, remember and skip bad/unexpected packets: - too short to hold the latency-related values - with bad signature - with invalid generator_id using a uint64_t-based bitmap. Also moved variable declarations closer to usage, added some likely/unlikely hints, reworked some return statements, and fixed 32-bit overflow (every ~4s) of rx_time_err computation. Change-Id: Ib2aadc1af6b7a68601cc080ba66b10d41ff9a64e Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
2018-06-29Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Updating release notes for OPNFV Fraser 6.2 Change-Id: I9a9da79cb4ccb245ddb38b50b561da51a40a359d Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-06-29Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Adding support for Ubuntu 17.10... Change-Id: I9a9da79cb4ccb245ccb38b50b561da51a40a359d Signed-off-by: Deepak S <deepak.s@linux.intel.com> - Adding centos.json to be used with packer to generate a VM with PROX Based on a CentOS cloud image downloadable from the web, you can now use packer to create an image that has DPDK and PROX installed in the proper directories. The VM is also tuned for guest VNFs. A service is also created to deal with the proper isolated_cpu settings for tuned. The service will also make sure uio and igb_uio are loaded. The prox_user_data.sh is not needed any more and hence deleted. ctrl-c of runrapid.py will now also stop prox in all the VMs so a new test can be started. Change-Id: I16cc59878e2d4912757f42e05f98d51dff5feb89 Signed-off-by: Luc Provoost <luc.provoost@intel.com> - TempFix: vCGNAPT/vACL ipv4 perf issue Change-Id: I924fcac7a65c0d221d5d422f419deb9c0f864172 Signed-off-by: Deepak S <deepak.s@linux.intel.com> - Temp Fix for vFW perf issue Change-Id: I324fcac7a65c0d221d5d422f419deb9c0f864172 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-06-28Update git submodulesEmma Foley1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Get multiple port stats simultaneously JIRA: YARDSTICK-1220 Implemented new "multi port stats <port list>" command, which returns a semi-colon-separated list of comma-separated values: - port id - total (at last_tsc) for rx_pkts, tx_pkts, no_mbufs, ierrors + imissed - last_tsc Change-Id: I8a8da79cb4ccb245ccb38b50b561da51a40a359d Signed-off-by: Patrice Buriez <patrice.buriez@intel.com> (cherry picked from commit a9d9979b1f5b7435552ae884da69220a42b81f81) Signed-off-by: Emma Foley <emma.l.foley@intel.com>
2018-05-25Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Updating release notes for OPNFV Fraser 6.1 Change-Id: I333fcac7a65c0d221d5d422f419deb9c0f864172 Signed-off-by: Deepak S <deepak.s@linux.intel.com> - Increase default mbuf size and code simplification/cleanup mbuf size was setup to achieve the best performance i.e. using the smallest mbuf and not segmenting packets. However this resulted in complex code, much dependent of the way the pmd are working e.g. a change(fix) in recent dpdk i40e implementation caused a 1782 (=1518+8+256) bytes mbuf to be too small to hold a 1518 bytes packets. Hence this change simplifies the mbuf size selection at the price of a potential decreases in performance - as more memory is now used. Except if jumbo frames are used, the mbuf size will now be the same for all modes. The packets will not be segmented except if jumbo frames are enabled. If jumbo frames are enabled, packets are by default segmented, except if the mbuf size is configured big enough in the config file. Change-Id: I222fcac7a65c0d221d5d422f419deb9c0f864172 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> Signed-off-by: Deepak S <deepak.s@linux.intel.com> - fix code standard in VNFs/DPPD-PROX/handle_esp.c Change-Id: I6c1a8f6d8e3bc84f7eb8e5780cde98dd9c03c805 Signed-off-by: Igor Shaula <igor.shaula@intel.com>
2018-04-26Update git submodulesXavier Simonart1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Fix crc offloads. When configuring a port, prox configures queue flags. For historitical reasons, offloads had to be disabled on some pmds. There is now an API to query the ports and gets their capabilities. This fix sets now the flags based on the capabilities, and not the driver name. Change-Id: Ic72d15001992f26910f653c70d31e4381fff8089 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> - Update Fraser document... Change-Id: I4ed02be7ca899db4f8f97355c180a92d69d38d8f Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-04-26Update git submodulesXavier Simonart1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Support reading inline jumbo frame and dump them Add support for pkt_inline of jumbo frames. Dump the whole packet, and not a truncated packet. This might have a small impact on performance as the memory footprint is increased (by ~640K * number of tasks), resulting in potential higher DTLB misses. Change-Id: I4ed02be7ca899db4f8f97355c180a92d69d39d8f Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> - Add support for generation of jumbo frames Change-Id: I63af4e5c5c01a4412d517e33fc7111481fd0524a Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> - Support for dpdk-stable-17.11.1 crypto Change-Id: I1a4aee3d550d007046be9d1677dd0ad980cb9817 Signed-off-by: Igor Shaula <igor.shaula@intel.com> - Fix memory leak introduced by 4a65cd84 Change-Id: I937bb38baa51d1902793fa8720a3ea740a583473 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> - Add support for multiple variables in core definition In the [core] definition we were able to use one variable such as $core1 in [core $core1] but not [core ${core1}]. The second syntax is used when we want multiple variables such as in [core ${first_core}-${last_core}]. This second syntax is now supported. Change-Id: Ic94b84cb8cf827acb6697789cd180f41c3bdb028 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-04-20Update git submodulesXavier Simonart1-0/+0
* Update docs/submodules/samplevnf from branch 'stable/fraser' - Fix link speed when link is down at startup. When link is down at startup, the link_speed returned by DPDK is 0. This results in un-optimized latency estimates in gen and lat. With this fix, lat and gen do nothing until link_speed is properly initialized, and use the right link speed in the fast path. Change-Id: Id2d14b6966ccfac7cc78db3c5a74e704b42edae7 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> - Support async operation in handle_esp Change-Id: Ibee77e31c0eb7a0e14e7aa0df092a278dfe75d6b Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> - Add support for reception of jumbo frames Jumbo frames are now supported through the addition of a "mtu" parameter of the port in the config file. Setting the mtu to a value higher than 1500 bytes will enable the reception of jumbo frames. In addition, the rte_eth_dev_set_mtu is now set for all pmds. Finally, setting mbuf_size does not set MEMPOOL_F_NO_SPREAD anymore. This option was only used for pure debugging. Big packets can be received using two ways - Using multiple "small" mbufs, i.e. around 2K. This is the default. - Using one big mbuf holding the whole packet. This can be enabled by setting a parameter mbuf_size in the receiving core configuration Change-Id: Idd60ad31f41c89f9522dff4d894af2696b7a2ea1 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> - Added missing file: rapidVMs.vms This file describes flavors, flavor meta data and boot info. All this info can be defined in the [Default] section and will then be used by to create all VMs. This data can also be specified in individual VM sections to overule the deault values per VM. Change-Id: I9d59208360eacec2790e5c467d7afcbeba301251 Signed-off-by: Luc Provoost <luc.provoost@intel.com> - Add support for multiple GEN tasks running on the same core resolve memory allocation issue Change-Id: I90bbf711a6a7a4869e5024c061470d9779839a60 Signed-off-by: Igor Shaula <igor.shaula@intel.com> - Add support for crypto on multiple cores * Experimental, for dpdk-stable-17.05.2 * New improved ESP decapsulation function Change-Id: If4862dacb3fcf53e21eb5932a195664f80c7c192 Signed-off-by: Igor Shaula <igor.shaula@intel.com>
2018-04-06Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Added missing file: rapidVMs.vms" - Added missing file: rapidVMs.vms This file describes flavors, flavor meta data and boot info. All this info can be defined in the [Default] section and will then be used by to create all VMs. This data can also be specified in individual VM sections to overule the deault values per VM. Change-Id: I9d59208360eacec2790e5c467d7afcbeba301251 Signed-off-by: Luc Provoost <luc.provoost@intel.com>
2018-04-06Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Add support for multiple GEN tasks running on the same core" - Add support for multiple GEN tasks running on the same core resolve memory allocation issue Change-Id: I90bbf711a6a7a4869e5024c061470d9779839a60 Signed-off-by: Igor Shaula <igor.shaula@intel.com>
2018-04-06Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Add support for crypto on multiple cores" - Add support for crypto on multiple cores * Experimental, for dpdk-stable-17.05.2 * New improved ESP decapsulation function Change-Id: If4862dacb3fcf53e21eb5932a195664f80c7c192 Signed-off-by: Igor Shaula <igor.shaula@intel.com>
2018-04-03Update git submodulesIgor Shaula1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Support additional MAC format in config file Add support for space-divided bytes in MAC string. Support the same format as in "pkt inline". Change-Id: I7f2136c4424c45ce4abad4082470c9c9b1b3ab05 Signed-off-by: Igor Shaula <igor.shaula@intel.com>
2018-03-28Update git submodulesLuc Provoost1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Replaced heat stack yaml files by individual server creation There is now a new file (rapidVMs.vms) describing how many VMs need to be created. You can specify the same flavor values in the [DEFAULT] section or specify specific flavors per VM. The heat stack yaml files are removed. Change-Id: Ic5ec485e8344a35e9ac9f6e8347adbc70520d10a Signed-off-by: Luc Provoost <luc.provoost@intel.com>
2018-03-26Update git submodulesPatrice Buriez1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Trivial: fix trailing white-spaces Makefile checks for some coding style rules. Previous commit introduced trailing white-spaces, which broke compilation. Change-Id: Ia57fc9b1428b4a9f8537dce4875e62ac55265fe3 Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
2018-03-16Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix potential crash if link speed is null" - Fix potential crash if link speed is null Link_speed could be null when prox started with the ports down. This was potentially causing a crash. Another task will need to update link speed when the port come up. Failing to do this results in less accurate latencies (no extrapolation) Change-Id: I597b68e30117e6edb9ccb4732c2acedd5eb8ac80 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-03-16Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix minimum latency" - Fix minimum latency Revert back part of commit 9fa316261d7d9 The function abs_diff was erroneously changed to diff_or_zero. This function was supposed to measure the difference between rx and tx time; when rx time overflowed and tx time not yet (i.e. rx time ~= 0 and tx_time ~=UINT32_MAX, this function added UINT32_MAX to rx_time. The name of the function was confusing and caused the previous commit. Net effect of previous commit was that every four seconds the minimum latency was 0 This commit reverse back to the original behavior, with a function name diff_time. Change-Id: Ia1b80e48a756cf5df411dcf58ca1cbc835214d13 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-03-16Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Adding Farser preliminary documentation Change-Id: I3bbd7897deb6e452068c07ef68d395affa4a4b50 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2018-02-22Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fixed the calculation of dropped packets and other changes" - Fixed the calculation of dropped packets and other changes * Calculation of aboslute and relative dropped packets was wrong and is now fixed. * ./createrapid.py has now an extra option to select custom availability zones for the different VMs. * Fixed a typo to create the flavor: hw:cpu_thread_policy * The generator config files have now the packet id & signature fields. See PROX for more details on this. * ./runrapid has now a new option --configonly. Default is False. If set to True, all configuration files will be copied to the VMS, but the tests are not started. This allows you to go to the VMs and manually start PROX. * In addition to the average latency, maximum latency is now also displayed. Change-Id: I3bbd7897deb6e452068c07ef68d3959ffa4a4b50 Signed-off-by: Luc Provoost <luc.provoost@intel.com>
2018-02-22Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Add support for comments in configuration variables" - Add support for comments in configuration variables This feature will enable the possibility to have many cores configured in a prox config file, and enable/disable them through variables. For instance, a [core $var1] section in a config file will result in [core 1] if $var1 = 1; the whole section and section content will be ignored if $var1=# Before this implementation, [#core 1] or [core #] was already treated as a commented out section (the whole section was commented). But there was no way to define a variable $var = # to comment a section through a variable. Note that in today's implementation any non numerical (except s, h, t, -) characteter in the [core] section header (and not only #) will cause the section to be ignored. It would probably be better to consider # (as maybe N/A and none) as comments, and everything else as error. This is however not supported by the change request. Change-Id: Id4e2b27a1f9b6d595e0b442dcd971ad44a502031 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-02-22Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix latency accuracy and dumping latencies to file" - Fix latency accuracy and dumping latencies to file - Also changed lat_info.tx_packet_index to uint64_t, so also did it for task_lat.prev_tx_packet_index and n_loss. - Adjusted format strings accordingly, and fixed some other formats. - Adjusted overflow increment to 2^32 (i.e. UINT32_MAX + 1). - Replaced hard-coded 64 with ACCURACY_BUFFER_SIZE (still hard-coded in handle_gen.c). Change-Id: Ia59f36e17c0797a2a958dbe3b2ac420263473524 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com> Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
2018-02-15Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Auto Generated INFO.yaml file" - Auto Generated INFO.yaml file INFO.yaml meant to be machine readable. This file was auto generated from an ldap lookup and your projects INFO file. Meeting times are not currently filled out. please ammend this patchset to complete Going forward comitter promotions should be done against this file. PTLs: Must be merged for you to gain delete access on testresults.opnfv.org If project_lead: is missing (my script could not parse) please amend with same from commiters section eg: project_lead: &opnfv_$project_ptl name: 'Lead Name' email: 'lead email' id: 'lead lfid' company: 'lead company' Change-Id: Ib034d62db7138a9f7c66c4d3377d6681764c41b4 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-02-15Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix potential crash in rx and tx distribution" - Fix potential crash in rx and tx distribution In some (rare) modes, more than 64 packets can be received through one rx function. This is for instance the case of the lat mode. Change-Id: Ie733c927a8e116c679c464f2551768185ef85366 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-02-12Update git submodulesLuc Provoost1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Zero packet loss testing has been added. Using l2 testing, where no ARP messages are being used, you can now run a zero packet loss test. The binary search will continue to find the speed where absolutely no packets have been lost during the test. On top of that, the output has been reformatted to also show the absolute and relative packet loss. The *.test files have now 2 new parameters: drop_rate_treshold and accuracy. When drop_rate_treshold is set to 0, this test will conclude successfull when no packet has been lost whatsoever. If this is set to any other number, the test will be successfull when the relative packet loss is lower than drop_rate_treshold. The new accuray parameter defines when the binary search will stop: when the relative difference between the min and max of the search window is lower than accuracy. The irq testing is slightly modified to print the total number of interrupts in a certain time bucket, not only as the number per second, but when there is no interrupt whatsowever, we print '0' in stead of '0.0' Change-Id: I8fafded0a225cbe1ba7ac61cd28e94d72099e4a0 Signed-off-by: Luc Provoost <luc.provoost@intel.com>
2018-02-04Update git submodulesLuc Provoost1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Fixed issues with the pkt_size command Fixed issues with pkt_size. For a 64 byte packet, we need to issue pkt_size <core> <task> 60 4 extra bytes will be calculated and added automatically by PROX Also added the missing irq.test and irq.cfg files Added support for OpenStack systems not using floating IP addresses Change-Id: I05d775eb858a58dd349ea370a0e34ac6448590c9 Signed-off-by: Luc Provoost <luc.provoost@intel.com>
2018-01-29Update git submodulesProvoost1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Rework of the test cases in the *.test files Cores can now be specified in the test files. An irq test has been added to verify if the VMs are not suffering from long interrupts. Change-Id: I647fda3ebf76c7c2b36a8df9a63d9fb83563c249 Signed-off-by: Provoost <luc.provoost@intel.com>
2018-01-25Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix dumping receive packets" - Fix dumping receive packets There were two issues identified in dump receive packets - when the receive packets was going to be dropped (and not transmitted), it was also printed as TX[255]. - a potential crash when using the dump function with modes like lat which can receive more than MAX_RING_BURST. Those issues have been fixed. Change-Id: Ia2297539d64961a211389d68e3c9c6280472243c Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-01-25Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Integrate irq mode into PROX (support display and command line)" - Integrate irq mode into PROX (support display and command line) irq mode can be used to show how a core is interrupted by other tasks. This mode does not handle packets. It only loops reading tsc. When the difference between two consecutive calls to rdtsc() is high then it means the core was interrupted. This task implementes the display, so that we can see a histogram of interrupts as well as the maximum, per core. Command line is also supported, through "show irq buckets" (too show the intervals of each buckets, in micrcoseconds), and the stats command line (showing the number of items in each buckets and the max).. Change-Id: I153cc3deaa7b86ae2776ea44e46ef9ecfd116992 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-01-25Update git submodulesXavier Simonart1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Fix extrapolation used in latency measurements When doing latency measurements PROX takes into account the generation or reception of a bulk of packets. For instance, if PROX receives at time T 4 packets, it knows that the first packet was received by te NIC before T (the time to receive the other 3 packets, as they were received at maximum link speed). So the latency data is decreased by the minimum time to receive those 3 packets. For this PROX was using a default link speed of 10Gbps. This is wrong for 1Gbps and 40Gbps networks, and was causing for instance issues on 40 Gbps networks as extrapolating too much, resulting in either too low latencies or negative numbers (visible as very high latencies). Change-Id: I4e0f02e8383dd8d168ac50ecae37a05510ad08bc Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-01-16Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Add support for DPDK 17.11" - Add support for DPDK 17.11 Change-Id: I5611ead4b61b23d6c1c983852e8c75619e08ecf9 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-01-16Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Add config option to use port mac as src mac in l2fwd and swap" - Add config option to use port mac as src mac in l2fwd and swap L2fwd and swap has many options to set src mac. swap was supposed to support the ability to use port mac, but config file parsing was wrong. L2fwd was using port mac if a port was available and if src mac=packet or if there was no src mac in the config. Now l2fwd supports the following options - "src mac=xx:xx:xx:xx:xx:xx" => this mac address is used as src mac. - "src mac=packet" => the src mac is taken from the dst mac of the received packet. - "src mac=hw" => the src mac is taken from the mac address of the port, if there is a physical port. Error otherwise. - "src mac=no" => src mac kept untouched - No "src mac" => same as "src mac=hw" if there is a physical port and same as "src mac=packet" otherwise. Default is (no "src mac") hence the mac is taken from the tx port if there is one tx port and from the packet otherwise. swap support is similar, except that it does not support "src mac=no". Change-Id: I70fe49a61c2e85772288b769ede14a7a6205d122 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-01-16Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix using signature in latency measurements" - Fix using signature in latency measurements When doing latency measurements the generator can add a 32 bits signature in the packet at a specific location, so that the receiver only uses the packets generated by the generator and ignores packets generated for instance by a switch The is particuly important for latency measurements as we use data in the packets as timestamps, and packets generated elsewhere would result in random latency for those packets. Change-Id: I8352b35aff76ec8d1344a1e492b9dcc20a53f1ce Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-01-16Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix stacking of rx receive functions" - Fix stacking of rx receive functions PROX can stack different RX functions, so that they are executed after each other. This feature is for instance used to dump packets or to print distribution of receive packets, without influencing the performance of the rx functions when no dump or print is needed. The previous implementation was wrong and causing some of the stacked functions not to be executed. This was causing for instance issues in latency measurement after enabling dumping packets. Change-Id: I766b8ee8e8852fa17cdaf60ee6e1fec0dc98c719 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-01-16Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix potential crash when issuing "tx distr stop" command." - Fix potential crash when issuing "tx distr stop" command. Change-Id: I9ef89020d203674f6c3301653ab2ff9d623665b6 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2018-01-05Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Initialize fields of outer IP header" - Initialize fields of outer IP header As it was non being initialized, fragment offset was sometimes non null. prox_ip_cksum_sw (as well as prox_ip_cksum_hw) require the hdr_checksum field to be initialized to 0. Change-Id: I3824682023782edb555982e558e5ae68062c3c9b Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-12-19Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Adding Security gateway testing" - Adding Security gateway testing Using now .test files describing the test to be executed. Also desribed in the README file how to deal with SRIOV ports. Change-Id: I3eb1551d7f205fef3fa1914bc6959c2126d63425 Signed-off-by: Provoost <luc.provoost@intel.com>
2017-12-19Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Add l3 support for tasks without physical tx ports" - Add l3 support for tasks without physical tx ports This adds support for tasks in l3 submode receiving from ports but transmitting to rings. ARP related information is exchanged between tasks through master core. Tasks transmitting to physical ports are responsible to transmit arp related packets. Tasks not transmitting to physical ports (and using rings) should not try to transmit arp packets. Transmitting arp packets through ring would be more complex, as we would need extra information (within the mbuf) to distinguish for instance an arp reply comoing from the network and an arp reply coming from a core (as a reply to an arp request). Change-Id: Ib55dc8c39d5e55703a933faa16bcc008f1274929 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-12-19Update git submodulesXavier Simonart1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Add support for multiple tasks generating to same ip in l3 mode. When multiple tasks generate to the same ip in l3 mode (i.e. with arp support), all those tasks generate arp requests. we need to make sure that they all receive a arp-reply i.e. that the master broadcast the reply to all those cores. Change-Id: I7e89196497a1016a94dde167f212b1f6ed03bcfe Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-12-15Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Updating release notes for OPNFV Euphrates 5.1 Change-Id: I01a619de621a3dfbfe11cabef257f9dec311e318 Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-12-08Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix command parser" - Fix command parser Command parser could have been crashing if a wrong core/task was used in pkt_size command. For some other commands both an error and a warning were printed in case of errors. Change-Id: I6648bfca1b5bcde3c6393d49687ed84900326d49 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-12-08Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix checks done when changing generator pkt_size" - Fix checks done when changing generator pkt_size Different checks were done when setting the generator pkt_size. In case of wrong pkt_size (e.g. too big) an error was printed but the pkt_size was still set causing a potential corruption. In addition, in case of a packet size incompatible with some of the packet fields (e.g. latency data) PROX was panicing while this should not happen runtime for such an error. Change-Id: Ifa11475bf295aaac7b0255c1bf9b5feed8ef90c4 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-12-08Update git submodulesXavier Simonart1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Fix qos statistics Packets dropped by QoS (because queues were full) were erroneously shown as idle cycles. There aee now shown as discarded packets. Change-Id: I01a619de621a3dfbfe11cabef257f9dec311e208 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-11-22Update git submodulesIgor Shaula1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - correct prox ipsec vnf reapply the latest changes (47355 and 47521) due to gerrit merge problem * fix crypto init for both encryptor and decryptor * improve performance: preallocate crypto op memory in init * finalize enabling routed ipsec traffic (proper IP/MAC addresses) * correct handling of dropped packets at encryptor * Fix receive packets with size > 1024 bytes Change-Id: I51cccc9bef0b9564ea1a3465ad28fb985eee06d1 Signed-off-by: Igor Shaula <igor.shaula@intel.com>
2017-11-21Update git submodulesIgor Shaula1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - fix prox crypto build Change-Id: I4ea54763871c18b1bd6cec9dbb926f18f0f5833f Signed-off-by: Igor Shaula <igor.shaula@intel.com>
2017-11-21Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Add support for nop mode with l3 submode" - Add support for nop mode with l3 submode The l3 submode was not supported in nop mode, as the nop mode uses some specific nop thread (and not generic). When L3 is specified, the nop mode must use the generic thread. In addition the l3 submode is implemented differently than other submodes. It is not supported through task_init structures (i.e. each task does not have to explicitely tell that it supports l3 submode). But this prevented to run both a nop with no submode and a nop with a l3 submode. Note that nop with l3 is usually not very useful - it handles arp (requests and response) but as nop, it does not swap IP addresses. So with a real switch, the packets transmitted will be received back... and l3 mode is usually mainly usefull when using a switch. However, there is at least one nop mode where l3 submode makes sense: when the nop does not transmit. In such cases, for instace used in conjunction with a gen l3, the nop receives all packets and forward the arp requests and responses to the master for handling. Change-Id: I992121db285ba25a11cbb494092a6afc6fe55a58 Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-11-21Update git submodulesIgor Shaula1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - * fix encryption: ESP packet format * fix traffic routing * enqueue packets in a bulk (improve crypto performance: TBD) * improve code clarity * fix crypto dequeuing * complete decryption path implementation * NOTE: the code works in a chain mode; crypto init to be fixed next Change-Id: I058a906f4f4f5691ebf25d2cdf5b5faded88e11d Signed-off-by: Igor Shaula <igor.shaula@intel.com>
2017-11-13Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Remove unused files in udp replay Change-Id: I8cbad85c607ca5148723ed3689eaed2c4967fb1d Signed-off-by: Deepak S <deepak.s@linux.intel.com>
2017-11-09Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Fix changing impair delay through command line" - Fix changing impair delay through command line Change-Id: I7797241a1d384fa184bdf4d73b81babb21f7383d Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-11-09Update git submodulesXavier Simonart1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Fix latency commands in l3 submode Change-Id: I9c46b57f98b566efc8ca3ea5966befe2a150315b Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
2017-11-07Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "Rework handle_esp.c (proto, DPDK<17.08, cleanup)" - Rework handle_esp.c (proto, DPDK<17.08, cleanup) - Adjust handle functions to PROX-v035+ prototype, returning 0 when all packets have been handled. - Because cryptodev API was modified in DPDK 17.08, many changes would be necessary to support it. For the moment, just exclude handle_esp.c from PROX build when using DPDK 17.08+, which will be supported later. - Cleanup: - consistent use of PROX_PANIC to cleanly fail on errors - consistent use of OUT_DISCARD to drop unhandled packets - remove "__attribute__((unused))" when parameter is actually used - remove unused defines, fields and variables Change-Id: I10d84fa184a866b4a5f87272875612aace5dd5b1 Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
2017-11-07Update git submodulesDeepak S1-0/+0
* Update docs/submodules/samplevnf from branch 'master' - Merge "lw_AFTR: IP Checksum required on generated packet." - lw_AFTR: IP Checksum required on generated packet. In lwAFTR (ipv6 de-encapsulate) the generated ipv4 packet requires an IP checksum, otherwise this packet is dropped in Openstack. (Openstack is much stricter than baremetal) Some fields in the header need to be initialized. Add flag in Makefile which when enabled will build to include the generate the IP checksum in the build. FLAG = GEN_DECAP_IPV6_TO_IPV4_CKSUM=y Not include in default build. Change-Id: If94e7cff64b03c66362021f05e48fb9265fc8210 Signed-off-by: Daniel Martin Buckley <daniel.m.buckley@intel.com>