All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v3 0/3] dumpcap and pdump patches for 24.07
Date: Wed,  3 Jul 2024 08:45:42 -0700	[thread overview]
Message-ID: <20240703154705.19192-1-stephen@networkplumber.org> (raw)
In-Reply-To: <20240529160933.282846-1-stephen@networkplumber.org>

Fix bug where dumpcap and pdump programs would leave resources
if killed with SIGTERM (or if file gets full).

Fix bug where dumpcap would always run on CPU 0 only.

v3 - combine and rebase these patches

Stephen Hemminger (3):
  app/dumpcap: handle SIGTERM and SIGHUP
  app/pdump: handle SIGTERM and SIGHUP
  dumpcap: add lcores option

 app/dumpcap/main.c | 45 +++++++++++++++++++++++++++++++++++++++++++--
 app/pdump/main.c   | 21 +++++++++++++++------
 2 files changed, 58 insertions(+), 8 deletions(-)

-- 
2.43.0


  parent reply	other threads:[~2024-07-03 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 20:49 [PATCH 0/2] dumpcap,pdump handle cleanup signals Stephen Hemminger
2024-02-26 20:49 ` [PATCH 1/2] app/dumpcap: handle SIGTERM and SIGHUP Stephen Hemminger
2024-02-26 20:49 ` [PATCH 2/2] app/pdump: " Stephen Hemminger
2024-02-27  9:59   ` Pattan, Reshma
2024-02-27 18:09     ` Stephen Hemminger
2024-05-29 16:08 ` [PATCH v2 0/2] Fix pdump and dumpcap leaks on SIGTERM Stephen Hemminger
2024-05-29 16:08   ` [PATCH v2 1/2] app/dumpcap: handle SIGTERM and SIGHUP Stephen Hemminger
2024-05-29 16:08   ` [PATCH v2 2/2] app/pdump: " Stephen Hemminger
2024-07-03 15:45   ` Stephen Hemminger [this message]
2024-07-03 15:45     ` [PATCH v3 1/3] app/dumpcap: " Stephen Hemminger
2024-07-03 15:45     ` [PATCH v3 2/3] app/pdump: " Stephen Hemminger
2024-07-03 15:45     ` [PATCH v3 3/3] dumpcap: add lcores option Stephen Hemminger
2024-07-23 13:22     ` [PATCH v3 0/3] dumpcap and pdump patches for 24.07 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=20240703154705.19192-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@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 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.