[dpdk-dev] Byte order of vlan_tci of rte_mbuf is different on different source

[zhang.xinghua1 at zte.com.cn]

When using I350 working on SR-IOV mode, we got confused that byte order 
of vlan_tci in the VF received packet descriptor is different when the
packet source is different.

1) Packets from VF to VF, the byte order is big-endian. (e.g. 0xF00)
2) Packets from PC to VF, the byte order is little-endian. (e.g. 0xF)

Below is the testing net-work:
        VM0            VM1             PC
        VF0            VF1              |
          |             |               |
          +------+------+               |
                 |                      |
                 PF                     |
             hypervisor                 |
             SR-IOV NIC                 |
                 |                      |
                 |        VLAN 15       |
                 +---------switch-------+


We make a breakpoint at the following line of eth_igb_recv_pkts, the 
vlan_tci
we observed that everytime.

uint16_t
eth_igb_recv_pkts(void *rx_queue, struct rte_mbuf **rx_pkts,
               uint16_t nb_pkts)

                /* Only valid if PKT_RX_VLAN_PKT set in pkt_flags */
                rxm->vlan_tci = rte_le_to_cpu_16(rxd.wb.upper.vlan);

Thanks.
 
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.