DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: "Lewis Donzis" <lew@perftech.com>, dev <dev@dpdk.org>,
	"Anatoly Burakov" <anatoly.burakov@intel.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	"Morten Brørup" <mb@smartsharesystems.com>
Subject: Re: [PATCH v2 1/2] contigmem: support including mapped buffers in core dump
Date: Tue, 19 Nov 2024 15:48:49 +0000	[thread overview]
Message-ID: <ZzyzYU4e0ndDsjQo@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20241028162606.48381738@sovereign>

On Mon, Oct 28, 2024 at 04:26:06PM +0300, Dmitry Kozlyuk wrote:
> 2024-10-26 06:43 (UTC-0500), Lewis Donzis:
> > Is the extra control necessary, i.e., why not just always do this and let
> > the EAL option control whether the pages get dumped?
> 
> I've been evaluating your suggestion and see no downsides,
> except contigmem default behavior change, but does it have non-DPDK users?
> If no one objects, I'll prepare v3 doing the following:
> 1) everything from v2,
> 2) except always mark contigmem buffers as dumpable,
> 3) add --dump-mapped back and make DPDK disable dumping by default.
> As a result, in order to include mapped memory in coredump:
> * FreeBSD will require only "--dump-mapped";
> * Linux will require both "coredump_filter" setup and "--dump-mapped".

That all seems very reasonable, but it is late in the release cycle at this
point. Do you think it would be good to just take the v2 as is for 24.11,
and then change things thereafter to have more dynamic/runtime control of
the dump-setting in 25.03? 

From compatibility viewpoint, I don't think there are any non-DPDK users,
so if behaviour with EAL doesn't change, I don't think having the kernel
module default be different matters as we go from one release to the next.

/Bruce

  parent reply	other threads:[~2024-11-19 15:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23 23:18 [PATCH] eal: support including mapped memory " Dmitry Kozlyuk
2024-10-24  2:19 ` Stephen Hemminger
2024-10-24  2:31 ` Stephen Hemminger
2024-10-24  7:07   ` Morten Brørup
2024-10-24  7:22 ` Morten Brørup
2024-10-24  8:25   ` Dmitry Kozlyuk
2024-10-24 12:55 ` Lewis Donzis
2024-10-24 16:38 ` Stephen Hemminger
2024-10-24 20:54   ` Dmitry Kozlyuk
2024-10-25  0:22     ` Dmitry Kozlyuk
2024-10-25 20:26 ` [PATCH v2 0/2] Hugepage inclusion " Dmitry Kozlyuk
2024-10-25 20:26   ` [PATCH v2 1/2] contigmem: support including mapped buffers " Dmitry Kozlyuk
2024-10-26 11:43     ` Lewis Donzis
2024-10-28 13:26       ` Dmitry Kozlyuk
2024-10-28 13:35         ` Lewis Donzis
2024-11-19 15:48         ` Bruce Richardson [this message]
2024-11-19 18:27           ` Dmitry Kozlyuk
2024-11-19 15:43     ` Bruce Richardson
2024-10-25 20:26   ` [PATCH v2 2/2] doc: add instruction for including hugepages " Dmitry Kozlyuk
2024-10-26  3:18   ` [PATCH v2 0/2] Hugepage inclusion " Morten Brørup

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=ZzyzYU4e0ndDsjQo@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=lew@perftech.com \
    --cc=mb@smartsharesystems.com \
    --cc=stephen@networkplumber.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).