patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Rafał Kozik" <rk@semihalf.com>
To: Luca Boccassi <bluca@debian.org>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/ena: TX L4 offloads should not be set in RX path
Date: Fri, 26 Jan 2018 14:51:37 +0100	[thread overview]
Message-ID: <CAMG3L4_dSL0d+0Uuka+CxxWpzCw47rszDrSYONHi48mVUQzSHw@mail.gmail.com> (raw)
In-Reply-To: <1516973949.10752.3.camel@debian.org>

Hello,

I send this patch to stable list by mistake. I misunderstood git-send
configuration.
Currently this patch is under review on dpdk-dev list
http://dpdk.org/ml/archives/dev/2018-January/089053.html.

I am very sorry about the trouble I caused, I assure you that it will
never happen again.

Kind regards,
Rafal Kozik

2018-01-26 14:39 GMT+01:00 Luca Boccassi <bluca@debian.org>:
> On Thu, 2018-01-25 at 16:12 +0100, Rafal Kozik wrote:
>> 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")
>> Cc: stable@dpdk.org
>>
>> Reported-by: Matthew Smith <mgsmith@netgate.com>
>> Signed-off-by: Rafal Kozik <rk@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,
>
> Hi,
>
> has a similar/related fix been applied to dpdk/master?
>
> --
> Kind regards,
> Luca Boccassi

  reply	other threads:[~2018-01-26 13:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 15:12 Rafal Kozik
2018-01-26 13:39 ` Luca Boccassi
2018-01-26 13:51   ` Rafał Kozik [this message]
2018-01-26 14:14     ` Luca Boccassi
  -- strict thread matches above, loose matches on Subject: below --
2018-01-25 15:10 Rafal Kozik

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=CAMG3L4_dSL0d+0Uuka+CxxWpzCw47rszDrSYONHi48mVUQzSHw@mail.gmail.com \
    --to=rk@semihalf.com \
    --cc=bluca@debian.org \
    --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).