DPDK patches and discussions
 help / color / mirror / Atom feed
From: Roger B Melton <rmelton@cisco.com>
To: Olivier Matz <olivier.matz@6wind.com>,
	zhang.xinghua1@zte.com.cn, dev@dpdk.org
Subject: Re: [dpdk-dev] Byte order of vlan_tci of rte_mbuf is different on different source
Date: Thu, 24 Aug 2017 10:16:47 -0400	[thread overview]
Message-ID: <b3fc03b7-0196-00ff-d454-d2c64a950de3@cisco.com> (raw)
In-Reply-To: <57230D3D.6070209@6wind.com>

Hi folks,

Resurrecting this old thread.  I ran across this issue recently in DPDK 
17.05, and it's also present in17.08.  It appears no fix was committed.  
I'm working on a solution, but if anyone has a fix in flight please let 
me know.

Regards,
Roger


On 4/29/16 3:29 AM, Olivier Matz wrote:
> Hi,
>
> On 04/25/2016 04:35 AM, zhang.xinghua1@zte.com.cn wrote:
>> 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);
> In rte_mbuf.h, it is specified that these values (vlan_tci and
> vlan_tci_outer) must be stored in CPU order.
>
> It's probably a driver or hardware issue. Note that in linux there is
> something that looks similar to your issue:
>
> http://lxr.free-electrons.com/source/drivers/net/ethernet/intel/igb/igb_main.c#L1278
>
>        /* On i350, i354, i210, and i211, loopback VLAN packets
>         * have the tag byte-swapped.
>         */
>        if (adapter->hw.mac.type >= e1000_i350)
>            set_bit(IGB_RING_FLAG_RX_LB_VLAN_BSWAP, &ring->flags);
>
> I think you could check if the same thing is done in the
> dpdk driver.
>
>
>> --------------------------------------------------------
>> 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.
>>
> This notice should be removed in public emails.
>
> Regards,
> Olivier
> .
>

      reply	other threads:[~2017-08-24 14:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25  2:35 zhang.xinghua1
2016-04-29  7:29 ` Olivier Matz
2017-08-24 14:16   ` Roger B Melton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b3fc03b7-0196-00ff-d454-d2c64a950de3@cisco.com \
    --to=rmelton@cisco.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.com \
    --cc=zhang.xinghua1@zte.com.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).