From: Luca Boccassi <bluca@debian.org>
To: Didier Pallard <didier.pallard@6wind.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [18.02 1/2] net/vmxnet3: gather offload data on first and last segment
Date: Mon, 30 Apr 2018 17:32:33 +0100 [thread overview]
Message-ID: <1525105953.23337.27.camel@debian.org> (raw)
In-Reply-To: <20180430162829.11029-1-didier.pallard@6wind.com>
On Mon, 2018-04-30 at 18:28 +0200, Didier Pallard wrote:
> [ backported from upstream commit
> 5e5ac26f958f10ef3f1b443ed74c13898cc82e87 ]
>
> Offloads are split between first and last segment of a packet.
> Call a single vmxnet3_rx_offload function that will contain all
> offload operations. This patch does not introduce any code
> modification.
>
> Pass a vmxnet3_hw as parameter to the function, it is not presently
> used in this patch, but will be later used for TSO offloads.
>
> Signed-off-by: Didier Pallard <didier.pallard@6wind.com>
> Acked-by: Yong Wang <yongwang@vmware.com>
>
> Conflicts:
> drivers/net/vmxnet3/vmxnet3_rxtx.c : do not change packet type
> behaviour on stable branch; continue to parse packet
> to return precise RTE_PTYPE_L3_IPV4, rather than returning
> RTE_PTYPE_L3_IPV4_UNKNOWN like in master branch.
> ---
> drivers/net/vmxnet3/vmxnet3_rxtx.c | 66 +++++++++++++++++++++-------
> ----------
Thanks, series applied
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2018-04-30 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 16:28 Didier Pallard
2018-04-30 16:28 ` [dpdk-stable] [18.02 2/2] net/vmxnet3: fix Rx offload information in multiseg packets Didier Pallard
2018-04-30 16:32 ` Luca Boccassi [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=1525105953.23337.27.camel@debian.org \
--to=bluca@debian.org \
--cc=didier.pallard@6wind.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).