All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anatoly Burakov <anatoly.burakov@intel.com>
To: dev@dpdk.org
Cc: erik.g.carrillo@intel.com
Subject: [dpdk-dev] [PATCH 0/2] Fix timer resource leak
Date: Tue, 25 Jun 2019 17:11:40 +0100	[thread overview]
Message-ID: <cover.1561478924.git.anatoly.burakov@intel.com> (raw)
In-Reply-To: <1557354906-2500-1-git-send-email-erik.g.carrillo@intel.com>

Previous attempts [1] at fixing the resource leak have been
deemed unsuccessful because of limitations around what
can be done without breaking the ABI. Now that we've
broken the EAL ABI, we can fix this issue properly.

This patchset is adding a new lock API, as well as fixes the
actual issue.

The patchset dependson the FreeBSD fixes [2], as well as the
mem config patchset [3].

[1] http://patches.dpdk.org/patch/53334/
[2] http://patches.dpdk.org/project/dpdk/list/?series=5161
[3] http://patches.dpdk.org/project/dpdk/list/?series=5162

Anatoly Burakov (2):
  eal: add internal locks for timer lib into EAL
  timer: fix resource leak in finalize

 lib/librte_eal/common/eal_common_mcfg.c       | 14 +++++++
 lib/librte_eal/common/eal_memcfg.h            |  2 +
 .../common/include/rte_eal_memconfig.h        | 18 ++++++++
 lib/librte_eal/rte_eal_version.map            |  2 +
 lib/librte_timer/rte_timer.c                  | 41 +++++++++++++------
 lib/librte_timer/rte_timer.h                  |  5 ++-
 6 files changed, 67 insertions(+), 15 deletions(-)

-- 
2.17.1

  parent reply	other threads:[~2019-06-25 16:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 19:00 [dpdk-dev] [PATCH] timer: fix resource leak in finalize Erik Gabriel Carrillo
2019-05-02  9:18 ` Burakov, Anatoly
2019-05-02 12:19   ` Carrillo, Erik G
2019-05-02 13:03     ` Burakov, Anatoly
2019-05-02 13:48       ` Carrillo, Erik G
2019-05-03 22:54 ` [dpdk-dev] [PATCH v2] " Erik Gabriel Carrillo
2019-05-07 11:03   ` Burakov, Anatoly
2019-05-07 22:04     ` Carrillo, Erik G
2019-05-08  8:49       ` Burakov, Anatoly
2019-05-08 23:01         ` Carrillo, Erik G
2019-05-09  7:44           ` Thomas Monjalon
2019-05-08 22:35   ` [dpdk-dev] [PATCH v3] " Erik Gabriel Carrillo
2019-05-09  8:29     ` Burakov, Anatoly
2019-06-05  9:33       ` Thomas Monjalon
2019-06-05  9:47         ` Burakov, Anatoly
2019-06-25 16:11     ` Anatoly Burakov [this message]
2019-06-25 16:11       ` [dpdk-dev] [PATCH 1/2] eal: add internal locks for timer lib into EAL Anatoly Burakov
2019-06-27 18:41         ` Carrillo, Erik G
2019-07-04  9:09         ` David Marchand
2019-07-04 10:44           ` Burakov, Anatoly
2019-06-25 16:11       ` [dpdk-dev] [PATCH 2/2] timer: fix resource leak in finalize Anatoly Burakov
2019-06-27 18:48         ` Carrillo, Erik G
2019-07-04  9:10         ` David Marchand
2019-07-04 10:45           ` Burakov, Anatoly
2019-07-04 10:50             ` David Marchand
2019-07-05 13:20       ` [dpdk-dev] [PATCH v2 0/1] Fix timer resource leak Anatoly Burakov
2019-07-05 13:20         ` [dpdk-dev] [PATCH v2 1/1] timer: fix resource leak in finalize Anatoly Burakov
2019-07-05 17:22         ` [dpdk-dev] [PATCH v3 0/1] Fix timer resource leak Anatoly Burakov
2019-07-05 17:22           ` [dpdk-dev] [PATCH v3 1/1] timer: fix resource leak in finalize Anatoly Burakov
2019-07-05 22:06             ` Thomas Monjalon

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=cover.1561478924.git.anatoly.burakov@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.