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 8697DA05D3 for ; Tue, 26 Mar 2019 15:05:06 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DD9C35B26; Tue, 26 Mar 2019 15:05:05 +0100 (CET) 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 4C5933424; Tue, 26 Mar 2019 10:05:02 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Tue, 26 Mar 2019 10:05:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=toAKOZNcw30mEvYHmIrUFAqmZdCbiV5yozcHR74XSPQ=; b=rH9tO2b4hinN dTNftcfDA+rTUC4qL82tUuU68SatRKoNhxi6ntghps+1UuZdOqVM8sDX1i66rnur iD1VC3BcunXIx1TMC1zqBei5YhoR+9DRU0Lw2GJmPIJlOvznf5hBAojXlV/Gs/Bv a/MvqKghaIZNaJKy3n/u5pUyo39v4V4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=toAKOZNcw30mEvYHmIrUFAqmZdCbiV5yozcHR74XS PQ=; b=0x3wA5LuL8KZwgKa134V4q+1jMhSh6m8UBsToq1E4qKd0xS0PYR/5e8OC BHOHGrq4j/G0clUEJmvwMe4x3HOd85VY82dZzq/OvibvmdLFAAkdAd9e7ZFyQRLX w4ThAx4ISHOBahNExO2PSK0Yc69JcznO/X/UId6IMzKfNPwvJYBcPSulrUjTNWhA VJH+NdGYH7lW1jodL+xkePpCIgllqnb0I3DDTNxc3REU6ts4HmDAklPnpVfXgv3J xwuwcOSP+yJ9APYk3qgVOKds2rWLDU9jwq/tCh4coS+dBsI8Rot8bGhKiryz8B+0 78kKf2p9ofPXhaPup6D5/JnkxbiwQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrkedtgdehkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 342991031A; Tue, 26 Mar 2019 10:05:00 -0400 (EDT) From: Thomas Monjalon To: Pavan Nikhilesh Bhagavatula Cc: Jerin Jacob Kollanukkaran , "dev@dpdk.org" Date: Tue, 26 Mar 2019 15:04:58 +0100 Message-ID: <1837377.3VPZUNT4eb@xps> In-Reply-To: <20190326132054.19176-1-pbhagavatula@marvell.com> References: <20190326125327.5264-1-pbhagavatula@marvell.com> <20190326132054.19176-1-pbhagavatula@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" 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: <20190326140458.Xrz0JGKnErj9YKN4pTeFMdC947Z1EzCWS18p4YM6cik@z> 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?