From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f172.google.com (mail-wr0-f172.google.com [209.85.128.172]) by dpdk.org (Postfix) with ESMTP id A0CF3952 for ; Fri, 10 Feb 2017 11:18:44 +0100 (CET) Received: by mail-wr0-f172.google.com with SMTP id 89so104232195wrr.2 for ; Fri, 10 Feb 2017 02:18:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=R1hYbBLj4/bEnFd0asKcMdPJj+Mm4RbBHMlJOyGAsxc=; b=xxUM4P8jNiXU/qpm7FFszox7GTlJFUU/xj8OFlGDdXVTQAU2NUFtAemro+cCmKYKQ9 fqZymIWNHIx2ZNYoOBVaXPx8qzHRigWKBW6H6vI5D5aYuzvCvBtcvDVnZ1rovbFTysNF HPqG14Cga65xVxHSIGT6GtNZA/rJZXCmlER6u6yqUD/y9OBZWGdVFvEM0qPyQC3nRwUf 2BamjWHRWCz/XCJglzXnBK7yESYgixoHPZugQJzFZL8/HiN62skutswt4CWRuGxn7lc5 3nt0KZEExzfLWS/zD2H/vs17Ky6zo/BYYhjoPU8AbOIu5urJXf2fhMr9jp6sP58yPM3G 2/+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=R1hYbBLj4/bEnFd0asKcMdPJj+Mm4RbBHMlJOyGAsxc=; b=PgOQ0KPChdcsYqyKZ/+mdn1AHiXaZzii0Xus+kKRfsu6wtMjI9vbnsZkeTASIE4uYA Eg+PTKLlxj1krQ0IVBtmKWy1GzF7sqOdN1naRRIonSYH3JnvmE+L9zfvOXzC0+jgn0ez s13lHe3HyMDiIK7b6TopevP1vjn3lyQ2hxk/MkyEwAXeHfWNUf+ukqYBNLvRKrrca3po +9iNMYIkOggObdAB6nUl3rr0VNaOqhTMrueyNUzXYN5QXH70B7TQsXSxREg1H0VoQYPy PjcacM9OPOgJHFjdjPAblunP91oegOgX+ZiVnk+FhK7fDsvOBQ7pSe3EZS3+XHiejnwq aB1w== X-Gm-Message-State: AMke39n000uRKYJtRVqd5H7Xb85VdHf86Cx8lZjrlKB7xfUnTGWEHv0QypJ4ajqRR/zTRP5T X-Received: by 10.223.164.207 with SMTP id h15mr6737935wrb.142.1486721924301; Fri, 10 Feb 2017 02:18:44 -0800 (PST) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id l37sm1963763wrc.41.2017.02.10.02.18.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 10 Feb 2017 02:18:43 -0800 (PST) From: Thomas Monjalon To: Qi Zhang Cc: dev@dpdk.org, jingjing.wu@intel.com Date: Fri, 10 Feb 2017 11:18:43 +0100 Message-ID: <3158466.ioj3dkTVO6@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <1486670383-5286-1-git-send-email-qi.z.zhang@intel.com> References: <1486670383-5286-1-git-send-email-qi.z.zhang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] eal: fix max number of interrupt request 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: , X-List-Received-Date: Fri, 10 Feb 2017 10:18:44 -0000 2017-02-09 14:59, Qi Zhang: > The max number of interrupt request is possible > be changed after rte_intr_callback_register, so > in get_max_intr, we need to check if nessesary to > update the max_intr. So you are using rte_intr_enable() to update the max_intr field in the case of VFIO_MSIX. What about MSI, INTX and UIO cases?