DPDK usage discussions
 help / color / mirror / Atom feed
From: Pavan Kumar <PAVANK@extremenetworks.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] DPDK KNI last 4 bytes of a frame truncated
Date: Tue, 23 Jan 2018 13:39:40 +0000	[thread overview]
Message-ID: <CY4PR04MB0280D5B7C2EDB6477C9B3E26CDE30@CY4PR04MB0280.namprd04.prod.outlook.com> (raw)



Hi,

I am trying to run example KNI application on Intel 82599ES 10-Gigabit. I see that the last 4 bytes of the frame are always truncated.
I did a quick dump of frame length in kni_ingress ().

pkts_burst[i]->pkt_len  = 268 bytes (Actual frame length from source is 272 bytes)

I did a ip4 typecast of the received mbuf, it shows ip4->total_length is 254, which is 4 bytes less than actual data I send. Below is the sample code I used to dump ipv4 frame length.

if (rte_be_to_cpu_16(ether_type) == ETHER_TYPE_IPv4) {
            ip4 = rte_pktmbuf_mtod_offset(mbuf, struct ipv4_hdr *, hdr_len);
            hdr_len += sizeof(struct ipv4_hdr);
            l4_proto = ip4->next_proto_id;
            printf ("ip pkt len %d\n", rte_be_to_cpu_16(ip4->total_length));
}

I came across a similar post/ release notes for I350 controller (Ref: IXA00372461) which says CRC stripping is always enabled and results in last 4 byte loss.
Is this a similar problem I am facing for 10G 82599 NIC using KNI ?

Thanks
Pavan

________________________________

DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary material and is solely for the use of the intended recipient. Any review, use, disclosure, distribution or copying of this transmittal is prohibited except by or on behalf of the intended recipient. If you have received this transmittal in error, please notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed.

                 reply	other threads:[~2018-01-23 13:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CY4PR04MB0280D5B7C2EDB6477C9B3E26CDE30@CY4PR04MB0280.namprd04.prod.outlook.com \
    --to=pavank@extremenetworks.com \
    --cc=users@dpdk.org \
    /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).