From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Subject: [dpdk-dev] [PATCH] eal: make max interrupt vectors configurable
Date: Tue, 26 Mar 2019 12:54:32 +0000 [thread overview]
Message-ID: <20190326125327.5264-1-pbhagavatula@marvell.com> (raw)
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Make max interrupt vectors configurable so that platforms can
choose interrupt vector limit.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
config/common_base | 1 +
lib/librte_eal/common/include/rte_eal_interrupts.h | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/config/common_base b/config/common_base
index 0b09a9348..e84f8a233 100644
--- a/config/common_base
+++ b/config/common_base
@@ -68,6 +68,7 @@ CONFIG_RTE_MAX_LCORE=128
CONFIG_RTE_MAX_NUMA_NODES=8
CONFIG_RTE_MAX_HEAPS=32
CONFIG_RTE_MAX_MEMSEG_LISTS=64
+CONFIG_RTE_MAX_INTERRUPT_VECTORS=32
# each memseg list will be limited to either RTE_MAX_MEMSEG_PER_LIST pages
# or RTE_MAX_MEM_MB_PER_LIST megabytes worth of memory, whichever is smaller
CONFIG_RTE_MAX_MEMSEG_PER_LIST=8192
diff --git a/lib/librte_eal/common/include/rte_eal_interrupts.h b/lib/librte_eal/common/include/rte_eal_interrupts.h
index 9d302f412..19e44019f 100644
--- a/lib/librte_eal/common/include/rte_eal_interrupts.h
+++ b/lib/librte_eal/common/include/rte_eal_interrupts.h
@@ -17,7 +17,7 @@
#ifndef _RTE_EAL_INTERRUPTS_H_
#define _RTE_EAL_INTERRUPTS_H_
-#define RTE_MAX_RXTX_INTR_VEC_ID 32
+#define RTE_MAX_RXTX_INTR_VEC_ID RTE_MAX_INTERRUPT_VECTORS
#define RTE_INTR_VEC_ZERO_OFFSET 0
#define RTE_INTR_VEC_RXTX_OFFSET 1
--
2.20.1
next reply other threads:[~2019-03-26 12:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 12:54 Pavan Nikhilesh Bhagavatula [this message]
2019-03-26 12:54 ` Pavan Nikhilesh Bhagavatula
2019-03-26 13:08 ` Jerin Jacob Kollanukkaran
2019-03-26 13:08 ` Jerin Jacob Kollanukkaran
2019-03-26 13:11 ` Pavan Nikhilesh Bhagavatula
2019-03-26 13:11 ` Pavan Nikhilesh Bhagavatula
2019-03-26 13:21 ` [dpdk-dev] [PATCH v2] " Pavan Nikhilesh Bhagavatula
2019-03-26 13:21 ` Pavan Nikhilesh Bhagavatula
2019-03-26 14:04 ` Thomas Monjalon
2019-03-26 14:04 ` Thomas Monjalon
2019-03-26 14:43 ` Bruce Richardson
2019-03-26 14:43 ` Bruce Richardson
2019-03-26 15:57 ` [dpdk-dev] [EXT] " Jerin Jacob Kollanukkaran
2019-03-26 15:57 ` Jerin Jacob Kollanukkaran
2019-03-31 14:55 ` [dpdk-dev] [PATCH v3] eal: increase max number of interrupt vectors Pavan Nikhilesh Bhagavatula
2019-03-31 14:55 ` Pavan Nikhilesh Bhagavatula
2019-04-02 12:32 ` Thomas Monjalon
2019-04-02 12:32 ` Thomas Monjalon
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=20190326125327.5264-1-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=thomas@monjalon.net \
/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).