DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: dev@dpdk.org, phil.yang@arm.com
Subject: Re: [dpdk-dev] [pull-request] next-eventdev 20.08 RC1
Date: Mon, 06 Jul 2020 11:57:23 +0200	[thread overview]
Message-ID: <1847250.g8tQzFMpDL@thomas> (raw)
In-Reply-To: <BYAPR18MB2424F654DD959BD03D8DF2EFC8680@BYAPR18MB2424.namprd18.prod.outlook.com>

05/07/2020 05:41, Jerin Jacob Kollanukkaran:
>   http://dpdk.org/git/next/dpdk-next-eventdev
> ----------------------------------------------------------------
> Harman Kalra (1):
>       event/octeontx: fix memory corruption
> Harry van Haaren (1):
>       examples/eventdev_pipeline: fix 32-bit coremask logic
> Pavan Nikhilesh (3):
>       event/octeontx2: fix device reconfigure
>       event/octeontx2: fix sub event type violation
>       event/octeontx2: improve datapath memory locality

Pulled patches above.

> Phil Yang (4):
>       eventdev: fix race condition on timer list counter
>       eventdev: use c11 atomics for lcore timer armed flag
>       eventdev: remove redundant code
>       eventdev: relax smp barriers with c11 atomics

I cannot merge this C11 series because of an ABI breakage:

      reply	other threads:[~2020-07-06  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-05  3:41 Jerin Jacob Kollanukkaran
2020-07-06  9:57 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1847250.g8tQzFMpDL@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=phil.yang@arm.com \


* 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).