Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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>
|
|
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>
|
|
Change-Id: I01a619de621a3dfbfe11cabef257f9dec311e318
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
|
|
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Change-Id: I4ea54763871c18b1bd6cec9dbb926f18f0f5833f
Signed-off-by: Igor Shaula <igor.shaula@intel.com>
|
|
|
|
* 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>
|
|
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>
|
|
Change-Id: I8cbad85c607ca5148723ed3689eaed2c4967fb1d
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
|
|
Change-Id: I9c46b57f98b566efc8ca3ea5966befe2a150315b
Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
|
|
Change-Id: I7797241a1d384fa184bdf4d73b81babb21f7383d
Signed-off-by: Xavier Simonart <xavier.simonart@intel.com>
|
|
|
|
|
|
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>
|
|
- 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>
|
|
Change-Id: Ie6d4e7ce22c27967117a446626f5923643397812
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
|
|
|
|
|
|
Change-Id: I389389e5317d1a9d0d79cc1762d6f15d8287e36a
Signed-off-by: Alexander Komarov <alexander.komarov@intel.com>
Signed-off-by: Alexander Komarov <izard.ak@gmail.com>
|
|
Change-Id: I087c9a9acf412a99f8425fd65d07db6c3b7a4af7
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I25ab50297cd7d2f80a5206ddc3c55ffad36bd8d8
Signed-off-by: Alexander Komarov <alexander.komarov@intel.com>
Signed-off-by: Alexander Komarov <izard.ak@gmail.com>
|
|
Change-Id: I71f8b419a8b28bc3c9208c8902b91d06bc4653de
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I0c2accf7e2c1f417b9823a0dfa1f356ff7730a3d
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I80bcbe616b8f2c64151de6e588c892de6c3dc8f1
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I4a38ac4f7a05b6a96fd9e0e8539aa76252ded3b0
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I1238aa72f178fb8744fdea688704ef7ff22c9c75
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I5c6854467bca41ab0ca5894e1a706a65eb68ef32
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
|
|
Change-Id: If9e92a2404214e91c682793622f097e28c11597d
Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
|
|
Change-Id: If7cc44f3b57a54aef510f729930e6f79bf83689e
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I44972071e41b67a5aec2adaf426ec84f54c4414e
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Review and update teh Developer guide for E-Release.
Change-Id: I88221fe6ea5bf3581c1dbf8bf6aaa31a628fff87
Signed-off-by: Anand B Jyoti <anand.b.jyoti@intel.com>
|
|
Change-Id: I6b78044beb21fdf07ad70d22c81bcca6ca955e63
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: Ib7f67bff93ce531f66be31c3fbd63ecbb33a46d8
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I366d915a05f58c5653de89c1c59ebd180904e080
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
JIRA: SAMPLEVNF-84
Update the documents with CLI command reference and Resolve the
jenkins build warnings.
Change-Id: I2bf22507758e1a13b648cc40d86495581fe0d981
Signed-off-by: Anand B Jyoti <anand.b.jyoti@intel.com>
|
|
JIRA: SAMPLEVNF-85
The ethernet header pointer initialization was wrong due to which
the MAC address were not updated. Hence the packets were not
reaching the destination.
Change-Id: I90a38bba8d26d5f481c6476e6995eed92970b6e3
Signed-off-by: Anand B Jyoti <anand.b.jyoti@intel.com>
|
|
JIRA: SAMPLEVNF-86
Due to this KW fix the arp pipeline is rejecting the commands
greater than PIPELINE_MAX_ARGS size. This is seen in arp_route_tbl
which can is becoming bigger in case of multi port setup.
This patch undo the KW fix which is causing issue with longer
parameters under ARPICMP pipeline.
Change-Id: I96ba3882b5fecc6ac2f7b75f11a63083b847bba5
Signed-off-by: Anand B Jyoti <anand.b.jyoti@intel.com>
|
|
Change-Id: Id9ad242c5147a1dc15a181baa2c5bd886335921c
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
This patch adds samplevnf openstack heat templates generated by
yardstick
Change-Id: I23295a9b66f91dc6a136a6106a46115f47da35d4
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
This patch fixes KW issues seen with the common code.
Change-Id: I4f90369152345ea2ea9316b04ac946c0c69fd7d1
Signed-off-by: Vishwesh M Rudramuni <vishwesh.m.rudramuni@intel.com>
|
|
JIRA: SAMPLEVNF-83
This patch fixes the klocwork reported issues
Change-Id: I190d024777be1bf53cdc97feca1e5934781f3582
Signed-off-by: Anand B Jyoti <anand.b.jyoti@intel.com>
|