From: Shrikrishna Khare <skhare@shri-linux.eng.vmware.com>
To: <garwilkie@gmail.com>
Cc: <skhare@vmware.com>, <dev@dpdk.org>,
George Wilkie <george.wilkie@intl.att.com>
Subject: Re: [dpdk-dev] [PATCH] vmxnet3: set unknown packet_type for non-ipv4 packets
Date: Wed, 17 Jan 2018 22:04:23 -0800 [thread overview]
Message-ID: <alpine.DEB.2.10.1801172204070.12208@shri-linux.eng.vmware.com> (raw)
In-Reply-To: <1515585942-10720-1-git-send-email-george.wilkie@intl.att.com>
On Wed, 10 Jan 2018, garwilkie@gmail.com wrote:
> From: George Wilkie <george.wilkie@intl.att.com>
>
> With bonding, after sending sufficient ipv4 packets,
> bond_ethdev_rx_burst_8023ad() no longer recognizes LACP packets
> because the packet_type is set to RTE_PTYPE_L3_IPV4.
> Ensure packet_type is reset for non-ipv4 packets in vmxnet3_rx_offload.
>
> Signed-off-by: George Wilkie <george.wilkie@intl.att.com>
Acked-by: Shrikrishna Khare <skhare@vmware.com>
> ---
> drivers/net/vmxnet3/vmxnet3_rxtx.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/vmxnet3/vmxnet3_rxtx.c b/drivers/net/vmxnet3/vmxnet3_rxtx.c
> index f9416f3..abea641 100644
> --- a/drivers/net/vmxnet3/vmxnet3_rxtx.c
> +++ b/drivers/net/vmxnet3/vmxnet3_rxtx.c
> @@ -674,6 +674,8 @@ vmxnet3_rx_offload(const Vmxnet3_RxCompDesc *rcd, struct rte_mbuf *rxm)
> if ((rcd->tcp || rcd->udp) && !rcd->tuc)
> rxm->ol_flags |= PKT_RX_L4_CKSUM_BAD;
> }
> + } else {
> + rxm->packet_type = RTE_PTYPE_UNKNOWN;
> }
> }
>
> --
> 2.7.4
>
>
next parent reply other threads:[~2018-01-18 6:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1515585942-10720-1-git-send-email-george.wilkie@intl.att.com>
2018-01-18 6:04 ` Shrikrishna Khare [this message]
2018-01-10 17:08 garwilkie
2018-01-18 12:02 ` Ferruh Yigit
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=alpine.DEB.2.10.1801172204070.12208@shri-linux.eng.vmware.com \
--to=skhare@shri-linux.eng.vmware.com \
--cc=dev@dpdk.org \
--cc=garwilkie@gmail.com \
--cc=george.wilkie@intl.att.com \
--cc=skhare@vmware.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).