![]() Now available: The Design and Implementation of the FreeBSD Operating System (Second Edition) |
|||||||||||||||||||||||||
|
[ source navigation ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]
FreeBSD/Linux Kernel Cross Reference
|
| Name | Size | Last modified (GMT) | Description | |
| Parent directory | 2023-01-29 19:52:53 | |||
| LICENSE | 2048 bytes | 2023-01-29 19:52:53 | ||
| README | 6914 bytes | 2023-01-29 19:52:53 | ||
| ice-1.3.27.0.pkg | 676216 bytes | 2023-01-29 19:52:53 |
1 OS Default Dynamic Device Personalization (DDP) Package 2 ====================================================================== 3 July 7, 2020 4 5 6 Contents 7 ======== 8 - Overview 9 - Safe Mode 10 - Notes 11 - Installation & Troubleshooting 12 - Legal 13 14 15 Overview 16 ======== 17 Devices based on the Intel(R) Ethernet 800 Series require a Dynamic Device 18 Personalization (DDP) package file to enable advanced features (such as dynamic 19 tunneling, Intel(R) Ethernet Flow Director, RSS, and ADQ). 20 21 DDP allows you to change the packet processing pipeline of a device by applying 22 a profile package to the device at runtime. Profiles can be used to, for 23 example, add support for new protocols, change existing protocols, or change 24 default settings. DDP profiles can also be rolled back without rebooting the 25 system. 26 27 The DDP package loads during device initialization. The driver checks to see if 28 the DDP package is present and compatible. If this file exists, the driver will 29 load it into the device. If the DDP package file is missing or incompatible 30 with the driver, the driver will go into Safe Mode where it will use the 31 configuration contained in the device's NVM. Refer to the Intel(R) Ethernet 32 Adapters and Devices User Guide for more information on Safe Mode. 33 34 A general-purpose, default DDP package is automatically installed with all 35 supported Intel Ethernet 800 Series drivers on supported operating systems. 36 Additional DDP packages are available to address needs for specific market 37 segments or targeted solutions. 38 39 The default DDP package supports the following: 40 - MAC 41 - EtherType 42 - VLAN 43 - IPv4 44 - IPv6 45 - TCP 46 - ARP 47 - UDP 48 - SCTP 49 - ICMP 50 - ICMPv6 51 - CTRL 52 - LLDP 53 - VXLAN-GPE 54 - VXLAN (non-GPE) 55 - Geneve 56 - GRE 57 - NVGRE 58 - RoCEv2 59 - MPLS (up to 5 consecutive MPLS labels in the outermost Layer 2 header group) 60 61 62 Safe Mode 63 ========= 64 Safe Mode disables advanced and performance features, and supports only basic 65 traffic and minimal functionality, such as updating the NVM or downloading a 66 new driver or DDP package. 67 68 Refer to the Intel(R) Ethernet Adapters and Devices User Guide for more details 69 on DDP and Safe Mode. 70 71 72 Notes 73 ===== 74 - You cannot update the DDP package if any PF drivers are already loaded. To 75 overwrite a package, unload all PFs and then reload the driver with the new 76 package. 77 78 - Except for Linux, you can only use one DDP package per driver, even if you 79 have more than one device installed that uses the driver. 80 81 - Only the first loaded PF per device can download a package for that device. 82 83 - If you are using DPDK, see the DPDK documentation at https://www.dpdk.org/ 84 for installation instructions and more information. 85 86 87 Installation and Troubleshooting 88 ================================ 89 90 Microsoft* Windows* 91 ------------------- 92 The DDP package is installed as part of the driver binary. You don't need to 93 take additional steps to install the DDP package file. 94 95 If you encounter issues with the DDP package file, download the latest driver. 96 97 98 ESX 99 --- 100 The DDP package is installed as part of the driver binary. You don't need to 101 take additional steps to install the DDP package file. 102 103 If you encounter issues with the DDP package file, download the latest driver. 104 105 106 FreeBSD 107 ------- 108 The FreeBSD driver automatically installs the default DDP package file during 109 driver installation. See the base driver README for general installation and 110 building instructions. 111 112 The DDP package loads during device initialization. The driver looks for the 113 ice_ddp module and checks that it contains a valid DDP package file. 114 115 If you encounter issues with the DDP package file, you may need to download an 116 updated driver or ice_ddp module. See the log messages for more information. 117 118 NOTE: It's important to do 'make install' during initial ice driver 119 installation so that the driver loads the DDP package automatically. 120 121 122 Linux 123 ----- 124 The Linux driver automatically installs the default DDP package file during 125 driver installation. Read the base driver README for general installation and 126 building instructions. 127 128 The DDP package loads during device initialization. The driver looks for 129 intel/ice/ddp/ice.pkg in your firmware root (typically /lib/firmware/ or 130 /lib/firmware/updates/) and checks that it contains a valid DDP package file. 131 The ice.pkg file is a symbolic link to the default DDP package file installed 132 by the linux-firmware software package or the out-of-tree driver installation. 133 134 If you encounter issues with the DDP package file, you may need to download an 135 updated driver or DDP package file. Refer to the log messages for more 136 information. 137 138 You can install specific DDP package files for different physical devices in 139 the same system. To install a specific DDP package: 140 141 1. Download the DDP package file (ice-x.x.x.x.zip) you want for your device. In 142 addition to licensing information and this README, this zip file contains the 143 following files: 144 ice-x.x.x.x.pkg 145 ice.pkg 146 147 NOTE: The ice.pkg file is a Linux symbolic link file pointing to 148 ice-x.x.x.x.pkg (in the same path). 149 150 2. Rename the ice-x.x.x.x.pkg file as ice-xxxxxxxxxxxxxxxx.pkg, where 151 'xxxxxxxxxxxxxxxx' is the unique 64-bit PCI Express device serial number (in 152 hex) of the device you want the package downloaded on. The filename must 153 include the complete serial number (including leading zeros) and be all 154 lowercase. For example, if the 64-bit serial number is b887a3ffffca0568, then 155 the file name would be ice-b887a3ffffca0568.pkg. 156 157 To find the serial number from the PCI bus address, you can use the following 158 command: 159 160 # lspci -vv -s af:00.0 | grep -i Serial 161 Capabilities: [150 v1] Device Serial Number b8-87-a3-ff-ff-ca-05-68 162 163 You can use the following command to format the serial number without the 164 dashes: 165 166 # lspci -vv -s af:00.0 | grep -i Serial | awk '{print $7}' | sed s/-//g 167 b887a3ffffca0568 168 169 3. Copy the renamed DDP package file to /lib/firmware/updates/intel/ice/ddp/. 170 If the directory does not yet exist, create it before copying the file. 171 172 4. Unload all of the PFs on the device. 173 174 5. Reload the driver with the new package. 175 176 NOTE: The presence of a device-specific DDP package file overrides the loading 177 of the default DDP package file. 178 179 180 Legal / Disclaimers 181 =================== 182 Copyright (c) 2019 - 2020, Intel Corporation. 183 184 Intel and the Intel logo are trademarks of Intel Corporation or its 185 subsidiaries in the U.S. and/or other countries. 186 187 *Other names and brands may be claimed as the property of others. 188 189 This software and the related documents are Intel copyrighted materials, and 190 your use of them is governed by the express license under which they were 191 provided to you ("License"). Unless the License provides otherwise, you may not 192 use, modify, copy, publish, distribute, disclose or transmit this software or 193 the related documents without Intel's prior written permission. 194 This software and the related documents are provided as is, with no express or 195 implied warranties, other than those that are expressly stated in the License.
[ source navigation ] [ identifier search ] [ freetext search ] [ file search ] [ list types ] [ track identifier ]
This page is part of the FreeBSD/Linux Linux Kernel Cross-Reference, and was automatically generated using a modified version of the LXR engine.