From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] eal: make max interrupt vectors configurable Date: Tue, 26 Mar 2019 15:04:58 +0100 Message-ID: <1837377.3VPZUNT4eb@xps> References: <20190326125327.5264-1-pbhagavatula@marvell.com> <20190326132054.19176-1-pbhagavatula@marvell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Jerin Jacob Kollanukkaran , "dev@dpdk.org" To: Pavan Nikhilesh Bhagavatula Return-path: Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by dpdk.org (Postfix) with ESMTP id 650585B1E for ; Tue, 26 Mar 2019 15:05:04 +0100 (CET) In-Reply-To: <20190326132054.19176-1-pbhagavatula@marvell.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 26/03/2019 14:21, Pavan Nikhilesh Bhagavatula: > From: Pavan Nikhilesh > > Make max interrupt vectors configurable so that platforms can > choose interrupt vector limit. What is the impact of setting a big value? Can we agree on a big enough value without introducing any config?