From: Patrick Robb <probb@iol.unh.edu>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: Re: [PATCH v2 0/3] malloc related cleanups
Date: Mon, 17 Jun 2024 13:48:15 -0400 [thread overview]
Message-ID: <CAJvnSUCStShFSGk4oPU8Ok7Kv7+o7bfaNuUV66pTTyzts1HQXw@mail.gmail.com> (raw)
In-Reply-To: <20240615160215.117401-1-stephen@networkplumber.org>
For CI Testing: re-applying to main and retesting because main was in
a bad state (now fixed by Maxime), causing a virtio_smoke fail on this
series.
https://git.dpdk.org/dpdk/commit/?id=6bdc14606724bc7fb3834d5ec59b1cccf98adf28
On Sat, Jun 15, 2024 at 12:02 PM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> The type parameter for malloc is only used for tracing.
> Fix documentation and don't pass through heap routines.
>
> Stephen Hemminger (3):
> rte_malloc: document that type is for tracing
> eal: remove type argument from internal routines
> event/sw: avoid snprintf truncation
>
> v2 - keep usage for tracing
> - combine event malloc type patch
>
> drivers/event/sw/iq_chunk.h | 2 --
> drivers/event/sw/sw_evdev.c | 2 +-
> lib/eal/common/eal_common_memzone.c | 6 ++---
> lib/eal/common/malloc_heap.c | 39 ++++++++++++-----------------
> lib/eal/common/malloc_heap.h | 7 +++---
> lib/eal/common/rte_malloc.c | 2 +-
> lib/eal/include/rte_malloc.h | 24 +++++++++---------
> 7 files changed, 35 insertions(+), 47 deletions(-)
>
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-06-17 17:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-25 18:23 [RFC 0/4] malloc type argument cleanup (part 1) Stephen Hemminger
2024-04-25 18:23 ` [RFC 1/4] rte_malloc: document that type is unused Stephen Hemminger
2024-04-25 18:31 ` Tyler Retzlaff
2024-04-25 18:42 ` Stephen Hemminger
2024-04-25 18:23 ` [RFC 2/4] devtools/cocci: add script to find unnecessary malloc type Stephen Hemminger
2024-04-25 18:24 ` [RFC 3/4] devtools/cocci: add script to find where rte_calloc should be used Stephen Hemminger
2024-04-25 18:24 ` [RFC 4/4] eal/malloc: remove type argument from internal malloc routines Stephen Hemminger
2024-04-26 16:16 ` Tyler Retzlaff
2024-04-26 22:52 ` Stephen Hemminger
2024-04-26 23:06 ` Tyler Retzlaff
2024-05-07 7:04 ` Morten Brørup
2024-04-26 21:32 ` [RFC 0/4] malloc type argument cleanup (part 1) Patrick Robb
2024-06-15 16:00 ` [PATCH v2 0/3] malloc related cleanups Stephen Hemminger
2024-06-15 16:00 ` [PATCH v2 1/3] rte_malloc: document that type is for tracing Stephen Hemminger
2024-06-15 16:00 ` [PATCH v2 2/3] eal: remove type argument from internal routines Stephen Hemminger
2024-06-15 16:00 ` [PATCH v2 3/3] event/sw: avoid snprintf truncation Stephen Hemminger
2024-06-15 21:40 ` [PATCH v2 0/3] malloc related cleanups Morten Brørup
2024-06-17 17:48 ` Patrick Robb [this message]
2024-06-18 14:44 ` [PATCH v3 0/2] malloc type cleanups Stephen Hemminger
2024-06-18 14:44 ` [PATCH v3 1/2] rte_malloc: document that type is for tracing Stephen Hemminger
2024-06-18 14:44 ` [PATCH v3 2/2] eal: remove type argument from internal routines Stephen Hemminger
2024-07-05 14:09 ` [PATCH v3 0/2] malloc type cleanups David Marchand
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=CAJvnSUCStShFSGk4oPU8Ok7Kv7+o7bfaNuUV66pTTyzts1HQXw@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).