The Design and Implementation of the FreeBSD Operating System, Second Edition
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
sys/contrib/dev/ice/

Version: -  FREEBSD  -  FREEBSD-13-STABLE  -  FREEBSD-13-0  -  FREEBSD-12-STABLE  -  FREEBSD-12-0  -  FREEBSD-11-STABLE  -  FREEBSD-11-0  -  FREEBSD-10-STABLE  -  FREEBSD-10-0  -  FREEBSD-9-STABLE  -  FREEBSD-9-0  -  FREEBSD-8-STABLE  -  FREEBSD-8-0  -  FREEBSD-7-STABLE  -  FREEBSD-7-0  -  FREEBSD-6-STABLE  -  FREEBSD-6-0  -  FREEBSD-5-STABLE  -  FREEBSD-5-0  -  FREEBSD-4-STABLE  -  FREEBSD-3-STABLE  -  FREEBSD22  -  l41  -  OPENBSD  -  linux-2.6  -  MK84  -  PLAN9  -  xnu-8792 
SearchContext: -  none  -  3  -  10 

Name Size Last modified (GMT) Description
Back Parent directory 2023-01-28 21:00:00
File LICENSE 2048 bytes 2023-01-28 20:59:59
File README 9334 bytes 2023-01-28 20:59:59
File ice-1.3.30.0.pkg 692660 bytes 2023-01-28 20:59:59

    1 OS Default Dynamic Device Personalization (DDP) Package
    2 ======================================================================
    3 May 12, 2022
    4 
    5 
    6 Contents
    7 ========
    8 - Overview
    9 - Supported Operating Systems
   10 - Safe Mode
   11 - Notes
   12 - Installation
   13 - Troubleshooting
   14 - Legal
   15 
   16 
   17 Overview
   18 ========
   19 Devices based on the Intel(R) Ethernet 800 Series require a Dynamic Device
   20 Personalization (DDP) package file to enable advanced features (such as dynamic
   21 tunneling, Intel(R) Ethernet Flow Director, RSS, and ADQ).
   22 
   23 DDP allows you to change the packet processing pipeline of a device by applying
   24 a profile package to the device at runtime. Profiles can be used to, for
   25 example, add support for new protocols, change existing protocols, or change
   26 default settings. DDP profiles can also be rolled back without rebooting the
   27 system.
   28 
   29 The DDP package loads during device initialization or driver runtime, depending
   30 on the operating system. The driver checks to see if the DDP package is present
   31 and compatible. If this file exists, the driver will load it into the device.
   32 If the DDP package file is missing or incompatible with the driver, the driver
   33 will go into Safe Mode where it will use the configuration contained in the
   34 device's NVM. Refer to the Intel(R) Ethernet Adapters and Devices User Guide
   35 for more information on Safe Mode.
   36 
   37 A general-purpose, default DDP package is automatically installed with all
   38 supported Intel Ethernet 800 Series drivers on supported operating systems.
   39 Additional DDP packages are available to address needs for specific market
   40 segments or targeted solutions.
   41 
   42 The default DDP package supports the following:
   43 - MAC
   44 - EtherType
   45 - VLAN
   46 - IPv4
   47 - IPv6
   48 - TCP
   49 - ARP
   50 - UDP
   51 - SCTP
   52 - ICMP
   53 - ICMPv6
   54 - CTRL
   55 - LLDP
   56 - VXLAN-GPE
   57 - VXLAN (non-GPE)
   58 - Geneve
   59 - GRE
   60 - NVGRE
   61 - RoCEv2
   62 - MPLS (up to 5 consecutive MPLS labels in the outermost Layer 2 header group)
   63 
   64 
   65 Supported Operating Systems
   66 ===========================
   67 This DDP package is supported on the following operating systems:
   68 - Microsoft* Windows Server*
   69 - Linux*
   70 - FreeBSD*
   71 - VMware* ESXi*
   72 
   73 Refer to the Intel(R) Ethernet Adapters and Devices User Guide for currently
   74 supported versions of these operating systems.
   75 
   76 
   77 Safe Mode
   78 =========
   79 Safe Mode disables advanced and performance features, and supports only basic
   80 traffic and minimal functionality, such as updating the NVM or downloading a
   81 new driver or DDP package.
   82 
   83 Refer to the Intel(R) Ethernet Adapters and Devices User Guide for more details
   84 on DDP and Safe Mode.
   85 
   86 
   87 Notes
   88 =====
   89 - In Linux, FreeBSD, and Windows, you cannot update the DDP package if any PF
   90 drivers are already loaded. To overwrite a package, unload all PFs and then
   91 reload the driver with the new package.
   92 
   93 - In ESXi, use esxcli to load and unload DDP packages for specific market
   94 segments during driver runtime.
   95  
   96 - In FreeBSD and Windows, you can only use one DDP package per driver, even if
   97 you have more than one device installed that uses the driver.
   98 
   99 - In Linux, FreeBSD, and Windows, only the first loaded PF per device can
  100 download a package for that device. In ESXi, you can load different DDP
  101 packages for different PFs associated with a device.
  102 
  103 - If you are using DPDK, see the DPDK documentation at https://www.dpdk.org/
  104 for installation instructions and more information.
  105 
  106 
  107 Installation
  108 ============
  109 
  110 Microsoft Windows
  111 -----------------
  112 TO INSTALL THE OS DEFAULT DDP PACKAGE:
  113 
  114 The default DDP package is installed as part of the driver binary. You don't
  115 need to take additional steps to install the DDP package file.
  116 
  117 
  118 FreeBSD
  119 -------
  120 TO INSTALL THE OS DEFAULT DDP PACKAGE:
  121 
  122 The FreeBSD driver automatically installs the default DDP package file during
  123 driver installation. See the base driver README for general installation and
  124 building instructions.
  125 
  126 The DDP package loads during device initialization. The driver looks for the
  127 ice_ddp module and checks that it contains a valid DDP package file.
  128 
  129 NOTE: It's important to do 'make install' during initial ice driver
  130 installation so that the driver loads the DDP package automatically.
  131 
  132 
  133 Linux
  134 -----
  135 TO INSTALL THE OS DEFAULT DDP PACKAGE:
  136 
  137 The Linux driver automatically installs the default DDP package file during
  138 driver installation. Read the base driver README for general installation and
  139 building instructions.
  140 
  141 The DDP package loads during device initialization. The driver looks for
  142 intel/ice/ddp/ice.pkg in your firmware root (typically /lib/firmware/ or
  143 /lib/firmware/updates/) and checks that it contains a valid DDP package file.
  144 The ice.pkg file is a symbolic link to the default DDP package file installed
  145 by the linux-firmware software package or the out-of-tree driver installation.
  146 
  147 
  148 TO INSTALL A DDP PACKAGE FOR SPECIFIC MARKET SEGMENTS:
  149 
  150 You can install specific DDP package files for different physical devices in
  151 the same system. To install a specific DDP package:
  152 
  153 1. Download the DDP package file (ice-x.x.x.x.zip) you want for your device. In
  154 addition to licensing information and this README, this zip file contains the
  155 following files:
  156     ice-x.x.x.x.pkg
  157     ice.pkg
  158 
  159 NOTE: The ice.pkg file is a Linux symbolic link file pointing to
  160 ice-x.x.x.x.pkg (in the same path).
  161 
  162 2. Rename the ice-x.x.x.x.pkg file as ice-xxxxxxxxxxxxxxxx.pkg, where
  163 'xxxxxxxxxxxxxxxx' is the unique 64-bit PCI Express device serial number (in
  164 hex) of the device you want the package downloaded on. The filename must
  165 include the complete serial number (including leading zeros) and be all
  166 lowercase. For example, if the 64-bit serial number is b887a3ffffca0568, then
  167 the file name would be ice-b887a3ffffca0568.pkg.
  168 
  169 To find the serial number from the PCI bus address, you can use the following
  170 command:
  171 
  172 # lspci -vv -s af:00.0 | grep -i Serial
  173 Capabilities: [150 v1] Device Serial Number b8-87-a3-ff-ff-ca-05-68
  174 
  175 You can use the following command to format the serial number without the
  176 dashes:
  177 
  178 # lspci -vv -s af:00.0 | grep -i Serial | awk '{print $7}' | sed s/-//g
  179 b887a3ffffca0568
  180 
  181 3. Copy the renamed DDP package file to /lib/firmware/updates/intel/ice/ddp/.
  182 If the directory does not yet exist, create it before copying the file.
  183 
  184 4. Unload all of the PFs on the device.
  185 
  186 5. Reload the driver with the new package.
  187 
  188 NOTE: The presence of a device-specific DDP package file overrides the loading
  189 of the default DDP package file.
  190 
  191 
  192 ESX
  193 ---
  194 TO INSTALL THE OS DEFAULT DDP PACKAGE:
  195 
  196 The default DDP package is installed as part of the driver binary. You don't
  197 need to take additional steps to install the DDP package file.
  198 
  199 TO INSTALL A DDP PACKAGE FOR SPECIFIC MARKET SEGMENTS:
  200 
  201 You must first install the Intel(R) ESXCLI Plug-In for Managing Intel(R)
  202 Ethernet Network Adapters to be able to install and load market-specific DDP
  203 packages. Download it from:
  204 https://www.intel.com/content/www/us/en/download/19380/intel-esxcli-plug-in-for-
  205 managing-intel-ethernet-network-adapters.html
  206 
  207 NOTE: ESXi support for DDP packages for specific market segments requires the
  208 following:
  209 - OS: ESXi 6.7 or higher
  210 - Driver: icen 1.9.1.x or higher
  211 - Tool: intnet 1.8.3.x or higher
  212 
  213 To install and load this DDP package:
  214 
  215 1. Download and install the esxcli plug-in from the URL above.
  216 
  217 2. Download the DDP package.
  218 
  219 3. Copy the DDP package file to the following location: /store/intel/icen/ddp/.
  220    If the directory does not yet exist, create it before copying the file.
  221 
  222 4. From the command prompt, run the following command to load the DDP package:
  223 
  224    # esxcli intnet ddp load -n <vmnicX> -p <ddp_file_name> -f
  225 
  226    Where:
  227     <vmnicX> = the name of the NIC
  228     <ddp_file_name> = the name of the DDP package to load
  229     -f = forces the package to load
  230 
  231     NOTE: This operation will cause the driver to reset.
  232 
  233 5. Wait for the load result status.
  234 
  235 
  236 To list all active DDP packages for all virtual NICs, run the following:
  237 
  238 # esxcli intnet ddp list
  239 
  240 To unload (roll back) a DDP package, run the following:
  241 
  242 # esxcli intnet ddp rollback -n <vmnicX> -f
  243 
  244 NOTE: This operation will cause the driver to reset.
  245 
  246 
  247 Troubleshooting
  248 ===============
  249 
  250 Microsoft Windows
  251 -----------------
  252 If you encounter issues with the DDP package file, download the latest driver.
  253 
  254 FreeBSD
  255 -------
  256 If you encounter issues with the DDP package file, you may need to download an
  257 updated driver or ice_ddp module. See the log messages for more information.
  258 
  259 Linux
  260 -----
  261 If you encounter issues with the DDP package file, you may need to download an
  262 updated driver or DDP package file. Refer to the log messages for more
  263 information.
  264 
  265 ESX
  266 ---
  267 If you encounter issues with the DDP package file, download the latest driver.
  268 
  269 
  270 Legal / Disclaimers
  271 ===================
  272 Copyright (c) 2019 - 2022, Intel Corporation.
  273 
  274 Intel and the Intel logo are trademarks of Intel Corporation or its
  275 subsidiaries in the U.S. and/or other countries.
  276 
  277 *Other names and brands may be claimed as the property of others.
  278 
  279 This software and the related documents are Intel copyrighted materials, and
  280 your use of them is governed by the express license under which they were
  281 provided to you ("License"). Unless the License provides otherwise, you may not
  282 use, modify, copy, publish, distribute, disclose or transmit this software or
  283 the related documents without Intel's prior written permission.
  284 This software and the related documents are provided as is, with no express or
  285 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.