From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] performance-thread: add software packet type parsing
Date: Tue, 17 Jan 2017 18:39:21 +0100 [thread overview]
Message-ID: <3080969.Crb1XnCNDq@xps13> (raw)
In-Reply-To: <1481901316-48216-1-git-send-email-tomaszx.kulasek@intel.com>
2016-12-16 16:15, Tomasz Kulasek:
> Last changes in Niantic and Fortville NIC drivers causes that
> vector Rx path is chosen by default in l3fwd-thread application.
> This path doesn't support propagation of hw packet type recognition
> to the packet_type field in mbuf, and packets cannot be classified
> properly.
>
> The approach to solve this problem is similar to the commit: 71a7e2424e07
> ("examples/l3fwd: fix using packet type blindly").
>
> To use sw packet analizer, new command line option "--parse-ptype" is
> introduced.
>
> Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-01-17 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 15:15 Tomasz Kulasek
2017-01-17 17:39 ` Thomas Monjalon [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=3080969.Crb1XnCNDq@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=tomaszx.kulasek@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).