DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Michał Krawczyk" <mk@semihalf.com>
To: Rafal Kozik <rk@semihalf.com>
Cc: dev@dpdk.org, Marcin Wojtas <mw@semihalf.com>,
	"Tzalik, Guy" <gtzalik@amazon.com>,
	 "Schmeilin, Evgeny" <evgenys@amazon.com>,
	"Matushevsky, Alexander" <matua@amazon.com>,
	"Chauskin, Igor" <igorch@amazon.com>
Subject: Re: [dpdk-dev] [PATCH] net/ena: TX L4 offloads should not be set in RX path
Date: Thu, 25 Jan 2018 17:13:58 +0100	[thread overview]
Message-ID: <CAJMMOfP59kjAAPA4TF7BojCkPGUyu_s+21NN7X1FJUsfYAzUfw@mail.gmail.com> (raw)
In-Reply-To: <1516894063-8551-1-git-send-email-rk@semihalf.com>

2018-01-25 16:27 GMT+01:00 Rafal Kozik <rk@semihalf.com>:
>
> Information about received packet type detected by NIC should be
> stored in packet_type field of rte_mbuf. TX L4 offload flags should
> not be set in RX path. Only fields that could be set in of_flags
> during packet receiving are information if L4 and L3 checksum is
> correct.
>
> Fixes: 1173fca25af9 ("ena: add polling-mode driver")
>
> Reported-by: Matthew Smith <mgsmith@netgate.com>
> Signed-off-by: Rafal Kozik <rk@semihalf.com>
Signed-off-by: Michal Krawczyk <mk@semihalf.com>
> ---
>  drivers/net/ena/ena_ethdev.c | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ena/ena_ethdev.c b/drivers/net/ena/ena_ethdev.c
> index 83e0ae2..1e2af80 100644
> --- a/drivers/net/ena/ena_ethdev.c
> +++ b/drivers/net/ena/ena_ethdev.c
> @@ -275,16 +275,17 @@ static inline void ena_rx_mbuf_prepare(struct rte_mbuf *mbuf,
>                                        struct ena_com_rx_ctx *ena_rx_ctx)
>  {
>         uint64_t ol_flags = 0;
> +       uint32_t packet_type = 0;
>
>         if (ena_rx_ctx->l4_proto == ENA_ETH_IO_L4_PROTO_TCP)
> -               ol_flags |= PKT_TX_TCP_CKSUM;
> +               packet_type |= RTE_PTYPE_L4_TCP;
>         else if (ena_rx_ctx->l4_proto == ENA_ETH_IO_L4_PROTO_UDP)
> -               ol_flags |= PKT_TX_UDP_CKSUM;
> +               packet_type |= RTE_PTYPE_L4_UDP;
>
>         if (ena_rx_ctx->l3_proto == ENA_ETH_IO_L3_PROTO_IPV4)
> -               ol_flags |= PKT_TX_IPV4;
> +               packet_type |= RTE_PTYPE_L3_IPV4;
>         else if (ena_rx_ctx->l3_proto == ENA_ETH_IO_L3_PROTO_IPV6)
> -               ol_flags |= PKT_TX_IPV6;
> +               packet_type |= RTE_PTYPE_L3_IPV6;
>
>         if (unlikely(ena_rx_ctx->l4_csum_err))
>                 ol_flags |= PKT_RX_L4_CKSUM_BAD;
> @@ -292,6 +293,7 @@ static inline void ena_rx_mbuf_prepare(struct rte_mbuf *mbuf,
>                 ol_flags |= PKT_RX_IP_CKSUM_BAD;
>
>         mbuf->ol_flags = ol_flags;
> +       mbuf->packet_type = packet_type;
>  }
>
>  static inline void ena_tx_mbuf_prepare(struct rte_mbuf *mbuf,
> --
> 2.7.4
>

  reply	other threads:[~2018-01-25 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 15:27 Rafal Kozik
2018-01-25 16:13 ` Michał Krawczyk [this message]
2018-01-26 15:48   ` 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=CAJMMOfP59kjAAPA4TF7BojCkPGUyu_s+21NN7X1FJUsfYAzUfw@mail.gmail.com \
    --to=mk@semihalf.com \
    --cc=dev@dpdk.org \
    --cc=evgenys@amazon.com \
    --cc=gtzalik@amazon.com \
    --cc=igorch@amazon.com \
    --cc=matua@amazon.com \
    --cc=mw@semihalf.com \
    --cc=rk@semihalf.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).