From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 01A1EA05D3 for ; Tue, 26 Mar 2019 15:43:24 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D5ABA6904; Tue, 26 Mar 2019 15:43:23 +0100 (CET) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id ED09B4C88 for ; Tue, 26 Mar 2019 15:43:21 +0100 (CET) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Mar 2019 07:43:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,271,1549958400"; d="scan'208";a="137406256" Received: from bricha3-mobl.ger.corp.intel.com ([10.237.221.35]) by orsmga003.jf.intel.com with SMTP; 26 Mar 2019 07:43:19 -0700 Received: by (sSMTP sendmail emulation); Tue, 26 Mar 2019 14:43:18 +0000 Date: Tue, 26 Mar 2019 14:43:17 +0000 From: Bruce Richardson To: Thomas Monjalon Cc: Pavan Nikhilesh Bhagavatula , Jerin Jacob Kollanukkaran , "dev@dpdk.org" Message-ID: <20190326144317.GC472084@bricha3-MOBL.ger.corp.intel.com> References: <20190326125327.5264-1-pbhagavatula@marvell.com> <20190326132054.19176-1-pbhagavatula@marvell.com> <1837377.3VPZUNT4eb@xps> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline In-Reply-To: <1837377.3VPZUNT4eb@xps> User-Agent: Mutt/1.11.2 (2019-01-07) Subject: Re: [dpdk-dev] [PATCH v2] eal: make max interrupt vectors configurable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190326144317.hxUfryhZ89whU1MfJv2q_XIb4bUr9BIpO9DeXucxGr8@z> On Tue, Mar 26, 2019 at 03:04:58PM +0100, Thomas Monjalon wrote: > 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? > Is it a value that needs to be set differently per-platform, perhaps?