Package will be downloaded first if the file exists. In the following paths in order: /lib/firmware/updates/intel/ice/ddpĪnd /lib/firmware/intel/ice/ddp. During initialization, the driver searches The device-specific DDP package filename is ice-00ccbbffffaa0568.pkg ForĮxample, if the NIC’s device serial number is 00-CC-BB-FF-FF-AA-05-68, Where ‘xxxxxx’ is the 64-bit PCIe Device Serial Number of the NIC. For a specific NIC, theĭDP package supposed to be loaded can have a filename: ice-xxxxxx.pkg, The default DDP package file name is ice.pkg. The E810 has a limitedįunctionality built in to allow PXE boot and other use cases, but theĭriver must download a package file during the driver initialization The Intel E810 requires a programmable pipeline package be downloadedīy the driver to support normal operations. User can enable the related hardware debug mask such as ICE_DBG_NVM: Hardware debug mask log support (default 0) IPHDR2 - Outer/Single IPv6 Header offset. IPHDR1 - Outer/Single IPv4 Header offset. TCPHDR2 - Reserved Table 27.9 Protocol extraction : ip_offset IPHDR2 TCPHDR1 - TCP header word 6, “Data Offset” and “Flags” fields. Table 27.8 Protocol extraction : tcp TCPHDR2 IPHDR1 - IPv6 header word 1, 16 low bits of the “Flow Label” field. Table 27.7 Protocol extraction : ipv6_flow IPHDR2 IPHDR2 - IPv6 header word 0, “Ver”, “Traffic class” and high 4 bits of IPHDR1 - IPv6 header word 3, “Next Header” and “Hop Limit” fields. Table 27.6 Protocol extraction : ipv6 IPHDR2 IPHDR2 - IPv4 header word 0, “Ver”, “Hdr Len” and “Type of Service” fields. IPHDR1 - IPv4 header word 4, “TTL” and “Protocol” fields. Table 27.5 Protocol extraction : ipv4 IPHDR2 VLAN1 - single or EVLAN (first for QinQ). Table 27.4 Protocol extraction : vlan VLAN2 The extraction metadata is copied into the registered dynamic mbuf field, and The offset of mbufĭynamic field is 92 for all queues with protocol extraction. IPv6 extraction, other queues use the default VLAN extraction. This setting means queues 1, 2-3, 8-9 are TCP extraction, queues 10-23 are Use pipeline mode by setting devargs parameter pipeline-mode-support,ĭpdk-testpmd -c 0xff -i port stop 0 port detach 0 port attach 18:00.0,proto_xtr=vlan,proto_xtr='', \ field_offs=92,field_name=pmd_dyn Rule or a switch rule depends on its pattern/action and the resource allocation situation,Īll flows are virtually at the same pipeline stage.īy default, generic flow API is enabled in none-pipeline mode, user can choose to Rules are created for device’s flow director engine.įor none-pipeline mode, priority is ignored, a flow rule can be created as a flow director Specific queue or queue group (we called it distribution stage), At this stage, flow !0 located at the second stage, typically packets are classified here and be steered to At this stage,įlow rules are created for the device’s exact match engine: switch. To drop the packet on a blocklist(we called it permission stage). Priority 0 located at the first pipeline stage which typically be used as a firewall Currently, we support two stages: priority = 0 or !0. In pipeline mode, a flow can be set at one specific stage by setting parameter Generic Flow Pipeline Mode Support (default 0) NOTE: In Safe mode, only very limited features are available, features like RSS,Ĭhecksum, fdir, tunneling … are all disabled. Then the driver will be initialized successfully and the device will enter Safe Mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |