• Q
    ice: Enable FDIR Configure for AVF · 1f7ea1cd
    Qi Zhang 提交于
    The virtual channel is going to be extended to support FDIR and
    RSS configure from AVF. New data structures and OP codes will be
    added, the patch enable the FDIR part.
    
    To support above advanced AVF feature, we need to figure out
    what kind of data structure should be passed from VF to PF to describe
    an FDIR rule or RSS config rule. The common part of the requirement is
    we need a data structure to represent the input set selection of a rule's
    hash key.
    
    An input set selection is a group of fields be selected from one or more
    network protocol layers that could be identified as a specific flow.
    For example, select dst IP address from an IPv4 header combined with
    dst port from the TCP header as the input set for an IPv4/TCP flow.
    
    The patch adds a new data structure virtchnl_proto_hdrs to abstract
    a network protocol headers group which is composed of layers of network
    protocol header(virtchnl_proto_hdr).
    
    A protocol header contains a 32 bits mask (field_selector) to describe
    which fields are selected as input sets, as well as a header type
    (enum virtchnl_proto_hdr_type). Each bit is mapped to a field in
    enum virtchnl_proto_hdr_field guided by its header type.
    
    +------------+-----------+------------------------------+
    |            | Proto Hdr | Header Type A                |
    |            |           +------------------------------+
    |            |           | BIT 31 | ... | BIT 1 | BIT 0 |
    |            |-----------+------------------------------+
    |Proto Hdrs  | Proto Hdr | Header Type B                |
    |            |           +------------------------------+
    |            |           | BIT 31 | ... | BIT 1 | BIT 0 |
    |            |-----------+------------------------------+
    |            | Proto Hdr | Header Type C                |
    |            |           +------------------------------+
    |            |           | BIT 31 | ... | BIT 1 | BIT 0 |
    |            |-----------+------------------------------+
    |            |    ....                                  |
    +-------------------------------------------------------+
    
    All fields in enum virtchnl_proto_hdr_fields are grouped with header type
    and the value of the first field of a header type is always 32 aligned.
    
    enum proto_hdr_type {
            header_type_A = 0;
            header_type_B = 1;
            ....
    }
    
    enum proto_hdr_field {
            /* header type A */
            header_A_field_0 = 0,
            header_A_field_1 = 1,
            header_A_field_2 = 2,
            header_A_field_3 = 3,
    
            /* header type B */
            header_B_field_0 = 32, // = header_type_B << 5
            header_B_field_0 = 33,
            header_B_field_0 = 34
            header_B_field_0 = 35,
            ....
    };
    
    So we have:
    proto_hdr_type = proto_hdr_field / 32
    bit offset = proto_hdr_field % 32
    
    To simply the protocol header's operations, couple help macros are added.
    For example, to select src IP and dst port as input set for an IPv4/UDP
    flow.
    
    we have:
    struct virtchnl_proto_hdr hdr[2];
    
    VIRTCHNL_SET_PROTO_HDR_TYPE(&hdr[0], IPV4)
    VIRTCHNL_ADD_PROTO_HDR_FIELD(&hdr[0], IPV4, SRC)
    
    VIRTCHNL_SET_PROTO_HDR_TYPE(&hdr[1], UDP)
    VIRTCHNL_ADD_PROTO_HDR_FIELD(&hdr[1], UDP, DST)
    
    The byte array is used to store the protocol header of a training package.
    The byte array must be network order.
    
    The patch added virtual channel support for iAVF FDIR add/validate/delete
    filter. iAVF FDIR is Flow Director for Intel Adaptive Virtual Function
    which can direct Ethernet packets to the queues of the Network Interface
    Card. Add/delete command is adding or deleting one rule for each virtual
    channel message, while validate command is just verifying if this rule
    is valid without any other operations.
    
    To add or delete one rule, driver needs to config TCAM and Profile,
    build training packets which contains the input set value, and send
    the training packets through FDIR Tx queue. In addition, driver needs to
    manage the software context to avoid adding duplicated rules, deleting
    non-existent rule, input set conflicts and other invalid cases.
    
    NOTE:
    Supported pattern/actions and their parse functions are not be included in
    this patch, they will be added in a separate one.
    Signed-off-by: NJeff Guo <jia.guo@intel.com>
    Signed-off-by: NYahui Cao <yahui.cao@intel.com>
    Signed-off-by: NSimei Su <simei.su@intel.com>
    Signed-off-by: NBeilei Xing <beilei.xing@intel.com>
    Signed-off-by: NQi Zhang <qi.z.zhang@intel.com>
    Tested-by: NChen Bo <BoX.C.Chen@intel.com>
    Signed-off-by: NTony Nguyen <anthony.l.nguyen@intel.com>
    1f7ea1cd
ice_lan_tx_rx.h 29.6 KB