From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Sunil Kumar Kori <skori@marvell.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Sunil Kumar Kori" <skori@marvell.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v3 1/1] examples/ip_frag: fix Tx fast free offload flag
Date: Thu, 25 Jul 2019 08:28:58 +0000 [thread overview]
Message-ID: <BYAPR18MB242427853CAECAF78245FDB4C8C10@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <1564043050-28306-1-git-send-email-skori@marvell.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Sunil Kumar Kori
> Sent: Thursday, July 25, 2019 1:54 PM
> To: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Sunil Kumar Kori <skori@marvell.com>
> Subject: [dpdk-dev] [PATCH v3 1/1] examples/ip_frag: fix Tx fast free offload
> flag
>
> Application uses different pool to allocate direct and indirect mbufs which are
> further spliced together to consturct a fragmented packet and same is
> transmitted over the port which is configured with
> DEV_TX_OFFLOAD_MBUF_FAST_FREE enabled i.e. all segments must belong
> to the same pool. But constructed packet violates the conditions.
>
> So fixing DEV_TX_OFFLOAD_MBUF_FAST_FREE flag during device
> configuration.
>
> Fixes: fdb9eff67f0c ("examples/ip_fragmentation: convert to new offloads
> API")
>
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
Reviewed-by: Jerin Jacob <jerinj@marvell.com>
next prev parent reply other threads:[~2019-07-25 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1564034330-16321-1-git-send-email-skori@marvell.com>
2019-07-25 8:24 ` [dpdk-stable] " Sunil Kumar Kori
2019-07-25 8:28 ` Jerin Jacob Kollanukkaran [this message]
2019-07-25 10:49 ` Ananyev, Konstantin
2019-07-29 21:46 ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
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=BYAPR18MB242427853CAECAF78245FDB4C8C10@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=skori@marvell.com \
--cc=stable@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).