From: Thomas Monjalon <thomas@monjalon.net>
To: Sunil Kumar Kori <skori@marvell.com>
Cc: dev@dpdk.org, "Ananyev,
Konstantin" <konstantin.ananyev@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 1/1] examples/ip_frag: fix Tx fast free offload flag
Date: Mon, 29 Jul 2019 23:46:08 +0200 [thread overview]
Message-ID: <2265276.8h4lJIiHNK@xps> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772580168A5B0A2@irsmsx105.ger.corp.intel.com>
> > 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>
>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-07-29 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 5:50 [dpdk-dev] [PATCH] examples/ip_fragmentation: fix DEV_TX_OFFLOAD_MBUF_FAST_FREE flag Sunil Kumar Kori
2019-07-25 5:58 ` [dpdk-dev] [PATCH v2 1/1] examples/ip_frag: " Sunil Kumar Kori
2019-07-25 7:54 ` Ananyev, Konstantin
2019-07-25 8:24 ` [dpdk-dev] [PATCH v3 1/1] examples/ip_frag: fix Tx fast free offload flag Sunil Kumar Kori
2019-07-25 8:28 ` Jerin Jacob Kollanukkaran
2019-07-25 10:49 ` Ananyev, Konstantin
2019-07-29 21:46 ` 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=2265276.8h4lJIiHNK@xps \
--to=thomas@monjalon.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.