From: Bruce Richardson <bruce.richardson@intel.com>
To: "Chen, Jing D" <jing.d.chen@intel.com>
Cc: Michael Frasca <michael.frasca@oracle.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] fm10k: set packet type for multi-segment packets
Date: Thu, 21 Apr 2016 15:03:50 +0100 [thread overview]
Message-ID: <20160421140350.GA3808@bricha3-MOBL3> (raw)
In-Reply-To: <4341B239C0EFF9468EE453F9E9F4604D04488388@shsmsx102.ccr.corp.intel.com>
On Mon, Apr 18, 2016 at 02:05:23PM +0000, Chen, Jing D wrote:
> Hi,
>
> > -----Original Message-----
> > From: Michael Frasca [mailto:michael.frasca@oracle.com]
> > Sent: Monday, April 18, 2016 8:52 PM
> > To: Chen, Jing D <jing.d.chen@intel.com>
> > Cc: dev@dpdk.org; Michael Frasca <michael.frasca@oracle.com>
> > Subject: [PATCH v2] fm10k: set packet type for multi-segment packets
> >
> > When building a chain of mbufs for a multi-segment packet, the packet_type
> > field resides at the end of the chain. It should be copied forward to the head
> > of the list.
> >
> > Also, uses RTE_LIBRTE_FM10K_RX_OLFLAGS_ENABLE to guard packet-type
> > computation. The mbuf fields are not copied when this define is not set.
> >
> > Fixes: fe65e1e1ce61 ("fm10k: add vector scatter Rx")
> >
> > Signed-off-by: Michael Frasca <michael.frasca@oracle.com>
> Acked-by : Jing Chen <jing.d.chen@intel.com>
>
Applied to dpdk-next-net/rel_16_07
/Bruce
prev parent reply other threads:[~2016-04-21 14:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 12:51 Michael Frasca
2016-04-18 14:05 ` Chen, Jing D
2016-04-21 14:03 ` Bruce Richardson [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=20160421140350.GA3808@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jing.d.chen@intel.com \
--cc=michael.frasca@oracle.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).