From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: david.marchand@redhat.com, ferruh.yigit@intel.com,
olivier.matz@6wind.com, mb@smartsharesystems.com,
konstantin.ananyev@intel.com, andrew.rybchenko@oktetlabs.ru,
viacheslavo@nvidia.com, ajit.khaparde@broadcom.com,
jerinj@marvell.com, hemant.agrawal@nxp.com
Subject: [dpdk-dev] [PATCH v2 0/2] move mbuf pool pointer
Date: Mon, 9 Nov 2020 22:29:35 +0100 [thread overview]
Message-ID: <20201109212937.989954-1-thomas@monjalon.net> (raw)
In-Reply-To: <20201107155306.463148-1-thomas@monjalon.net>
After some discussions, it seems the best option is still to use
the remaining space in the first half to move the pool pointer.
The fields move has an impact on octeontx2 in 32-bit build.
v2: disable octeontx2 drivers in 32-bit build.
Thomas Monjalon (2):
drivers: disable OCTEON TX2 in 32-bit build
mbuf: move pool pointer in first half
doc/guides/rel_notes/deprecation.rst | 7 -------
drivers/common/octeontx2/meson.build | 18 ++++++------------
drivers/crypto/octeontx2/meson.build | 17 +++--------------
drivers/event/octeontx2/meson.build | 18 ++++++------------
drivers/mempool/octeontx2/meson.build | 18 ++++++------------
drivers/net/octeontx2/meson.build | 11 ++++++-----
drivers/regex/octeontx2/meson.build | 22 +++-------------------
lib/librte_kni/rte_kni_common.h | 3 ++-
lib/librte_mbuf/rte_mbuf.h | 1 -
lib/librte_mbuf/rte_mbuf_core.h | 5 ++---
lib/librte_mbuf/rte_mbuf_dyn.c | 1 -
11 files changed, 34 insertions(+), 87 deletions(-)
--
2.28.0
next prev parent reply other threads:[~2020-11-09 21:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 15:53 [dpdk-dev] [PATCH 1/1] mbuf: move pool pointer in first half Thomas Monjalon
2020-11-07 17:12 ` Jerin Jacob
2020-11-07 18:39 ` Thomas Monjalon
2020-11-07 19:05 ` Jerin Jacob
2020-11-07 20:33 ` Thomas Monjalon
2020-11-09 5:18 ` Jerin Jacob
2020-11-09 8:04 ` Thomas Monjalon
2020-11-09 8:27 ` Jerin Jacob
2020-11-09 9:47 ` Bruce Richardson
2020-11-09 12:01 ` Jerin Jacob
2020-11-09 12:59 ` Thomas Monjalon
2020-11-09 13:35 ` Jerin Jacob
2020-11-09 14:02 ` Thomas Monjalon
2020-11-09 14:08 ` Jerin Jacob
2020-11-09 14:42 ` Thomas Monjalon
2020-11-09 14:53 ` Jerin Jacob
2020-11-09 8:16 ` Morten Brørup
2020-11-09 10:06 ` [dpdk-dev] [dpdk-techboard] " Bruce Richardson
2020-11-09 10:21 ` Morten Brørup
2020-11-09 18:04 ` Stephen Hemminger
2020-11-10 7:15 ` Morten Brørup
2020-11-07 18:57 ` [dpdk-dev] " Morten Brørup
2020-11-09 10:08 ` Bruce Richardson
2020-11-09 10:30 ` Morten Brørup
2020-11-09 10:33 ` Ananyev, Konstantin
2020-11-09 10:36 ` Bruce Richardson
2020-11-09 11:24 ` Ananyev, Konstantin
2020-11-09 21:29 ` Thomas Monjalon [this message]
2020-11-09 21:29 ` [dpdk-dev] [PATCH v2 1/2] drivers: disable OCTEON TX2 in 32-bit build Thomas Monjalon
2020-11-10 18:05 ` Jerin Jacob
2020-11-09 21:29 ` [dpdk-dev] [PATCH v2 2/2] mbuf: move pool pointer in first half Thomas Monjalon
2020-11-10 10:05 ` Morten Brørup
2020-11-10 10:44 ` Thomas Monjalon
2020-11-10 16:25 ` Olivier Matz
2020-11-10 18:06 ` Jerin Jacob
2020-11-12 14:39 ` Thomas Monjalon
2020-11-10 18:08 ` Stephen Hemminger
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=20201109212937.989954-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=mb@smartsharesystems.com \
--cc=olivier.matz@6wind.com \
--cc=viacheslavo@nvidia.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).