DPDK patches and discussions
 help / color / mirror / Atom feed
From: Paul Emmerich <emmericp@net.in.tum.de>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] add flag to disable CRC checksum offloading
Date: Mon, 15 Feb 2016 17:55:22 +0100	[thread overview]
Message-ID: <1455555325-20046-1-git-send-email-emmericp@net.in.tum.de> (raw)

This patch adds a new tx checksum offloading flag: PKT_TX_NO_CRC_CSUM.
This allows disabling CRC checksum offloading on a per-packet basis.
Doing this can be useful if you want to send out invalid packets on
purpose, e.g. in a packet generator/test framework.


Paul Emmerich (3):
  add tx crc disable flag
  ixgbe: use crc checksum disable flag
  i40e: use crc checksum disable flag

             reply	other threads:[~2016-02-15 16:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 16:55 Paul Emmerich [this message]
2016-02-15 16:55 ` [dpdk-dev] [PATCH 1/3] add tx crc disable flag Paul Emmerich
2016-03-04  9:18   ` Olivier MATZ
2016-02-15 16:55 ` [dpdk-dev] [PATCH 2/3] ixgbe: use crc checksum " Paul Emmerich
2016-02-15 16:55 ` [dpdk-dev] [PATCH 3/3] i40e: " Paul Emmerich
2016-03-02 21:15 ` [dpdk-dev] [PATCH 0/3] add flag to disable CRC checksum offloading Bruce Richardson

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=1455555325-20046-1-git-send-email-emmericp@net.in.tum.de \
    --to=emmericp@net.in.tum.de \
    --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).