DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Benson, Bryan" <bmbenson@amazon.com>
To: Daniel Kaminsky <daniel.kaminsky@infinitelocality.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] TX IP checksum offloading
Date: Thu, 7 Nov 2013 17:06:06 +0000	[thread overview]
Message-ID: <A029A4295D154649BCC3E22A692B26022DE0B3@ex10-mbx-36002.ant.amazon.com> (raw)
In-Reply-To: <CA+8v-JziNxf5e=m-y-JEeRyoRnpk14rmXo3X5acasV3ocdbbMw@mail.gmail.com>

Hi Daniel,
I posted some findings yesterday that seem relevant.  Try using the ol flags when you use an RX free threshold below 32.

I am looking into what can be done to fix it for values of 32 and above.
http://dpdk.org/ml/archives/dev/2013-November/000724.html

Thanks,
Bryan Benson
________________________________________
From: dev [dev-bounces@dpdk.org] on behalf of Daniel Kaminsky [daniel.kaminsky@infinitelocality.com]
Sent: Thursday, November 07, 2013 4:52 AM
To: dev@dpdk.org
Subject: [dpdk-dev] TX IP checksum offloading

Hi,

Did anyone had an experience using the PKT_TX_IP_CKSUM flag?
I have an application that generates IP traffic but whenever I try to set
this flag on (*m->ol_flags = PKT_TX_IP_CKSUM)* the rte_mbuf nothing is sent
out.
Retrieving that statistics from the ethernet device show zero for opackets
and oerrors.

I'm using ixgbe driver and DPDK 1.5.0-8 (from Intel) distribution.

Thanks,
Daniel

  reply	other threads:[~2013-11-07 17:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 12:52 Daniel Kaminsky
2013-11-07 17:06 ` Benson, Bryan [this message]
2013-11-07 21:05 ` Vladimir Medvedkin
2013-11-10 15:59   ` Daniel Kaminsky

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=A029A4295D154649BCC3E22A692B26022DE0B3@ex10-mbx-36002.ant.amazon.com \
    --to=bmbenson@amazon.com \
    --cc=daniel.kaminsky@infinitelocality.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).