DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wu, Yanglong" <yanglong.wu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] net/i40e: illegal packet checking
Date: Fri, 22 Jun 2018 11:52:58 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115323BA15@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180620021247.134575-1-yanglong.wu@intel.com>



> -----Original Message-----
> From: Wu, Yanglong
> Sent: Wednesday, June 20, 2018 10:13 AM
> To: dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; Wu, Yanglong <yanglong.wu@intel.com>
> Subject: [PATCH v4] net/i40e: illegal packet checking
> 
> Some illegal packets will lead to TX/RX hang and can't recover automatically.
> This patch check those illegal packets and protect TX/RX from hanging.
> 
> Signed-off-by: Yanglong Wu <yanglong.wu@intel.com>

Applied to dpdk-next-net-intel

Thanks!
Qi>

      parent reply	other threads:[~2018-06-22 11:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07  9:39 [dpdk-dev] [PATCH] net/i40e: illagel pactket checking Yanglong Wu
2018-06-07 16:04 ` Ananyev, Konstantin
2018-06-08  3:54 ` [dpdk-dev] [PATCH v2] " Yanglong Wu
2018-06-08 14:04   ` Ananyev, Konstantin
2018-06-08 17:24   ` Wiles, Keith
2018-06-15  6:18   ` [dpdk-dev] [PATCH v3] " Yanglong Wu
2018-06-15 14:56     ` Zhang, Qi Z
2018-06-19  8:42   ` [dpdk-dev] [PATCH v3] net/i40e: illegal " Yanglong Wu
2018-06-19  9:10   ` [dpdk-dev] [PATCH] " Yanglong Wu
2018-06-20  1:44   ` Yanglong Wu
2018-06-20  1:46   ` [dpdk-dev] [PATCH v3] " Yanglong Wu
2018-06-20  2:12     ` [dpdk-dev] [PATCH v4] net/i40e: illegal packet checking Yanglong Wu
2018-06-22  9:17       ` Ananyev, Konstantin
2018-06-22 11:52       ` Zhang, Qi Z [this message]

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=039ED4275CED7440929022BC67E706115323BA15@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=konstantin.ananyev@intel.com \
    --cc=yanglong.wu@intel.com \
    /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).