From: Aaron Conole <aconole@redhat.com>
To: Olivier Matz <olivier.matz@6wind.com>
Cc: dev@dpdk.org, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Pallantla Poornima <pallantlax.poornima@intel.com>,
Wenwu Ma <wenwux.ma@intel.com>,
Peng Zhihong <zhihongx.peng@intel.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v3 2/2] mbuf: better document usage of packet pool initializers
Date: Tue, 27 Apr 2021 10:22:43 -0400 [thread overview]
Message-ID: <f7t1rav3iz0.fsf@redhat.com> (raw)
In-Reply-To: <20210427135646.871-2-olivier.matz@6wind.com> (Olivier Matz's message of "Tue, 27 Apr 2021 15:56:46 +0200")
Olivier Matz <olivier.matz@6wind.com> writes:
> Clarify that the mempool private initializer and object initializer used
> for packet pools require that the mempool private size is large enough.
>
> Also add an assert (only enabled when -DRTE_ENABLE_ASSERT is passed) to
> check this constraint.
>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
> ---
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2021-04-27 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 21:05 [dpdk-dev] [PATCH] test/mempool: Fix illegal pointer access in mempool test Wenwu Ma
2021-04-13 20:05 ` [dpdk-dev] [v2] test/mempool: fix heap buffer overflow Wenwu Ma
2021-04-13 11:52 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2021-04-15 6:45 ` Olivier Matz
2021-04-15 12:51 ` Aaron Conole
2021-04-16 7:20 ` Olivier Matz
2021-04-27 13:56 ` [dpdk-dev] [PATCH v3 1/2] " Olivier Matz
2021-04-27 13:56 ` [dpdk-dev] [PATCH v3 2/2] mbuf: better document usage of packet pool initializers Olivier Matz
2021-04-27 14:22 ` Aaron Conole [this message]
2021-05-04 18:07 ` [dpdk-dev] [dpdk-stable] [PATCH v3 1/2] test/mempool: fix heap buffer overflow Thomas Monjalon
2021-04-15 2:04 ` [dpdk-dev] [PATCH] test/mempool: Fix illegal pointer access in mempool test Peng, ZhihongX
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=f7t1rav3iz0.fsf@redhat.com \
--to=aconole@redhat.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=pallantlax.poornima@intel.com \
--cc=thomas@monjalon.net \
--cc=wenwux.ma@intel.com \
--cc=zhihongx.peng@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.