Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp615819pxx; Mon, 26 Oct 2020 17:01:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyn7v3YCE9/wx5DdH/oExl4mxpAvlWJAIfq+fAiTNjTs7RcKL07wa8a9WULS5MvB65qj1U6 X-Received: by 2002:a17:906:23f2:: with SMTP id j18mr17805753ejg.526.1603756861699; Mon, 26 Oct 2020 17:01:01 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603756861; cv=none; d=google.com; s=arc-20160816; b=EDRsHa//1iPqSs7uB7gprUni82P7LNrl91IFjGd+WwFDCO1faJj9Pi7wPWJJMn06jb uEfg4IZsnwSY3naXFy4SjArHTVr/UbgSZJ8OblEHvZxhL0kLcywMxClM0l9UswJfyo8i nvBGyHq8+HsErxTaU45HeQvA0mjnGPTV62Z9E8P2eLPRZqgyCCjoot5zBFdRs7gfSXF/ UcSPc4rzGFE28MQ3GscV64Dex6GU5qS4SYvl1xthutZVM77bsjBj8ClYQrdTKzGiv0u5 qgY3ebqbjEhUVOKdsjKnW1kozLO3bQ7+c4qbc0XbzNkhug0POlG+lC9z2VsAdoBo2ADk VUww== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:message-id:date:references :in-reply-to:subject:cc:to:dkim-signature:dkim-signature:from; bh=y+PS6gYDSMvwJoN1FTHRdqvfX6lNIJ+gYdIEt2bNoQ8=; b=N9WU6xUfY8P+dXYsuSLpxWhGwB5yH08rFLWhkeoAClvjsyBDPPS3kxbPDnGkmkfuHy 9kgWT5S5NMKHXMquFhOB4cq7XF/+N/hF2iMTrUHCCcS3p4MhZAJsNPiYJAmu+YK0ZB1h GS8fwjFP/OLYdHob0AkeoABE890ap6lQF948rHLp4a3+a78gkXvD6WFTF1ahKo5l6Iw/ aCYJRoSWLbmMGJy9KbA6ShW5xuRhxOpHC0cJwJ3dsUGEege0JAR6NybsYWpgHMOqZ9EA uRDmplWSHS3C/oF6ex7wgfsiFFIrbo0O8J2xJDQXYkRto+0dmK4wFW7S+ZOIUq2csyTP Am8Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=kdQzswCG; dkim=neutral (no key) header.i=@linutronix.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d19si7949639edp.276.2020.10.26.17.00.39; Mon, 26 Oct 2020 17:01:01 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linutronix.de header.s=2020 header.b=kdQzswCG; dkim=neutral (no key) header.i=@linutronix.de; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=linutronix.de Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730342AbgJZULF (ORCPT + 99 others); Mon, 26 Oct 2020 16:11:05 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:42196 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730303AbgJZULE (ORCPT ); Mon, 26 Oct 2020 16:11:04 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1603743062; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=y+PS6gYDSMvwJoN1FTHRdqvfX6lNIJ+gYdIEt2bNoQ8=; b=kdQzswCGzg3Z+6EV7q0nZNMNXJ8qc9zZqXMPiqOeSORB6v2cw6FuaMmBBBt3doPeVr32cL 3Yc6LqeIgyNTfswN6zM6Aj84d6/Sb2E/hCRNiO2jZt4GEkAoOHzd8BTnn/XkFoJr1WsqKE sizuxIbXYyMhe21s0gUlWhv9xlStvpfjpV5bOp/neVVPm7i+Jauf8Pz3jDa0cfiOc8ZYFn pisu4H5ia1WUolOQKfrKF7nWkcH5WpR1ub7fhRk2dvExBoucgRUnvdwe9//eYaRIN/KjW7 cHdP5iVEDTNMYJWdZd2Fy39vXX0oWbq9HDQj5ctUlZR2viB/IAiV+nXli6769g== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1603743062; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=y+PS6gYDSMvwJoN1FTHRdqvfX6lNIJ+gYdIEt2bNoQ8=; b=75kDgynk1PiCyVqyRR1lvYBAb/SvfUPyH4B4xZqU8aMuSg9TGlvtaEz7zktx1sVq92mIKw qpgsGbcLl8lpunAQ== To: Jacob Keller , Marcelo Tosatti Cc: Nitesh Narayan Lal , Peter Zijlstra , helgaas@kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-pci@vger.kernel.org, intel-wired-lan@lists.osuosl.org, frederic@kernel.org, sassmann@redhat.com, jesse.brandeburg@intel.com, lihong.yang@intel.com, jeffrey.t.kirsher@intel.com, jlelli@redhat.com, hch@infradead.org, bhelgaas@google.com, mike.marciniszyn@intel.com, dennis.dalessandro@intel.com, thomas.lendacky@amd.com, jiri@nvidia.com, mingo@redhat.com, juri.lelli@redhat.com, vincent.guittot@linaro.org, lgoncalv@redhat.com Subject: Re: [PATCH v4 4/4] PCI: Limit pci_alloc_irq_vectors() to housekeeping CPUs In-Reply-To: <86f8f667-bda6-59c4-91b7-6ba2ef55e3db@intel.com> References: <20201019111137.GL2628@hirez.programming.kicks-ass.net> <20201019140005.GB17287@fuller.cnet> <20201020073055.GY2611@hirez.programming.kicks-ass.net> <078e659e-d151-5bc2-a7dd-fe0070267cb3@redhat.com> <20201020134128.GT2628@hirez.programming.kicks-ass.net> <6736e643-d4ae-9919-9ae1-a73d5f31463e@redhat.com> <260f4191-5b9f-6dc1-9f11-085533ac4f55@redhat.com> <20201023085826.GP2611@hirez.programming.kicks-ass.net> <9ee77056-ef02-8696-5b96-46007e35ab00@redhat.com> <87ft6464jf.fsf@nanos.tec.linutronix.de> <20201026173012.GA377978@fuller.cnet> <875z6w4xt4.fsf@nanos.tec.linutronix.de> <86f8f667-bda6-59c4-91b7-6ba2ef55e3db@intel.com> Date: Mon, 26 Oct 2020 21:11:02 +0100 Message-ID: <87v9ew3fzd.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 26 2020 at 12:21, Jacob Keller wrote: > On 10/26/2020 12:00 PM, Thomas Gleixner wrote: >> How does userspace know about the driver internals? Number of management >> interrupts, optimal number of interrupts per queue? > > I guess this is the problem solved in part by the queue management work > that would make queues a thing that userspace is aware of. > > Are there drivers which use more than one interrupt per queue? I know > drivers have multiple management interrupts.. and I guess some drivers > do combined 1 interrupt per pair of Tx/Rx.. It's also plausible to to > have multiple queues for one interrupt .. I'm not sure how a single > queue with multiple interrupts would work though. For block there is always one interrupt per queue. Some Network drivers seem to have seperate RX and TX interrupts per queue. Thanks, tglx