DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Neil Horman <nhorman@tuxdriver.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] ethdev: add new offload flag to keep CRC
Date: Mon, 11 Jun 2018 08:25:09 -0700	[thread overview]
Message-ID: <20180611082509.4551fac5@xeon-e3> (raw)
In-Reply-To: <20180608225709.19473-1-ferruh.yigit@intel.com>

On Fri,  8 Jun 2018 23:57:09 +0100
Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> DEV_RX_OFFLOAD_KEEP_CRC offload flag added.
> 
> DEV_RX_OFFLOAD_CRC_STRIP flag will remain one more release
> default behavior in PMDs is to keep the CRC until this flag removed

This won't work for virtual devices that never keep CRC.
Maybe wording should be changed.

  parent reply	other threads:[~2018-06-11 15:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-08 22:57 Ferruh Yigit
2018-06-09 10:11 ` Andrew Rybchenko
2018-06-11  9:18   ` Ferruh Yigit
2018-06-11 15:25 ` Stephen Hemminger [this message]
2018-06-19 12:54   ` Ferruh Yigit
2018-06-19 18:02 ` [dpdk-dev] [PATCH] " Ferruh Yigit
2018-06-20  7:42   ` Andrew Rybchenko
2018-06-20 17:24     ` Ferruh Yigit
2018-06-20 17:39       ` Andrew Rybchenko
2018-06-20 18:12         ` Ferruh Yigit
2018-06-20 21:16           ` Andrew Rybchenko
2018-06-20 10:54   ` Legacy, Allain
2018-06-20 13:44   ` Shahaf Shuler
2018-06-20 16:12     ` Ferruh Yigit
2018-06-21  7:53       ` Shahaf Shuler
2018-06-21 13:14   ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2018-06-28 23:46     ` Thomas Monjalon
2018-06-29 12:41     ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2018-06-29 11:57       ` Thomas Monjalon
2018-06-29 16:33         ` Ferruh Yigit

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=20180611082509.4551fac5@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=nhorman@tuxdriver.com \
    --cc=thomas@monjalon.net \
    /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).