DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Li Feng <fengli@smartx.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>, dev@dpdk.org
Subject: Re: [PATCH v2] eal/linux: enable the hugepage mem dump
Date: Wed, 2 Oct 2024 09:46:54 -0700	[thread overview]
Message-ID: <20241002094654.3fb762f6@hermes.local> (raw)
In-Reply-To: <20220401091004.3227117-1-fengli@smartx.com>

On Fri,  1 Apr 2022 17:10:04 +0800
Li Feng <fengli@smartx.com> wrote:

> These hugepages include important structures. we should dump these
> hugepages into a coredump file for debugging when generating a coredump.
> 
> Signed-off-by: Li Feng <fengli@smartx.com>

This needs to be config option to avoid surprising existing users.

      parent reply	other threads:[~2024-10-02 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220308094125.2716847-1-fengli@smartx.comOD>
2022-04-01  9:10 ` Li Feng
2022-04-05 22:46   ` Stephen Hemminger
2022-04-05 23:14     ` Dmitry Kozlyuk
2023-07-05 23:19       ` Stephen Hemminger
2022-04-06  2:11     ` Li Feng
2024-10-02 16:46   ` Stephen Hemminger [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:
  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=20241002094654.3fb762f6@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengli@smartx.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).