DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Benson, Bryan" <bmbenson@amazon.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] RX checksum offloading
Date: Thu, 7 Nov 2013 00:00:05 +0000	[thread overview]
Message-ID: <A029A4295D154649BCC3E22A692B26022DD412@ex10-mbx-36002.ant.amazon.com> (raw)

All,
Has anyone had any experience with hardware checksum offloads not working?  It appears that the combination of settings we are using in our application may be the crux of the issue, as offloading test-pmd application in csum mode correctly identifies bad packets via the ol_flags.  I am a bit stumped in tracking it down, any help is greatly appreciated!

We are using the 82599 NIC & DPDK 1.3 (with RSC disabled).

Settings:


/* Ethernet Configuration */
static struct rte_eth_conf port_conf = {
    .rxmode = {
        .split_hdr_size = 0,
        .header_split   = 0, /**< Header Split disabled */
        .hw_ip_checksum = 1, /**< IP/UDP/TCP checksum offload enabled. */
        .hw_vlan_filter = 0, /**< VLAN filtering disabled */
        .jumbo_frame    = 0, /**< Jumbo Frame Support disabled */
        .hw_strip_crc   = 1, /**< CRC stripped by hardware */
    },
    .rx_adv_conf = {
        .rss_conf = {
            .rss_key = NULL,
            .rss_hf  = 0x00,
        },
    },
    .txmode = {
    },
};

Thank you,
Bryan Benson
Amazon Web Services

             reply	other threads:[~2013-11-07  0:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07  0:00 Benson, Bryan [this message]
2013-11-07  3:09 ` Benson, Bryan
2013-11-07  3:44   ` Benson, Bryan
2013-11-07  9:06     ` Thomas Monjalon
2013-11-07 11:44       ` Thomas Monjalon
2013-11-07 21:53         ` Benson, Bryan
2013-11-07 21:50 Benson, Bryan
2013-11-08 10:27 ` Thomas Monjalon

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=A029A4295D154649BCC3E22A692B26022DD412@ex10-mbx-36002.ant.amazon.com \
    --to=bmbenson@amazon.com \
    --cc=dev@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).