Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp4843831imd; Tue, 30 Oct 2018 08:13:05 -0700 (PDT) X-Google-Smtp-Source: AJdET5etZCUkg8Ft5ST+NA3Y1X9WqmEQYYuAjdabqAc40lMsj4BU9e1yKYjQy+ztPXhUkKMmgJz1 X-Received: by 2002:a63:588:: with SMTP id 130mr18258486pgf.273.1540912385067; Tue, 30 Oct 2018 08:13:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540912385; cv=none; d=google.com; s=arc-20160816; b=s7tk5hnfNcCaad+lLZH7y/I60eKEHxjN/R40KvFYlknU9asmY3CozHEERhJ0z0YxPm M7alf9QgnH/UOJ/9389tT0yJkx9DLPVWB3JbUYcnvc2SXZg7wCXasCJYl6+lyU/XsWtw p40CyuWs9DyJOJacd6P28rvRTBO1iZlXPsoAsFO0/az0eFJzlIN7KfUGPXuMAu5XKeoj quViyzIxLUEMH7VI3C2sho+m0C9I3Dc9uYQ2+jhkz5QrDFFonF/uAzlw5cNlI/b1N5UG kWwqKHxKQftikUHD0GvSxu8L6nKqq/Hk60MfI85DBn2DpwDchwClUmUAoDCeBwioH21q Aw8w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=fgNlvPCW/ft0q00LrlRdmQMOGmhXOcokCEtwUpX1KhE=; b=dSfcYg9NhKh/NJrAs51OV/bfl4a5LlxKwspBms/89VdVtPxdIgZQWsZigopJFVg8oL whXBgTIbtnRWNGQ9+CC4vjT/rbW4j2rR/bZyqfDlxd+m9IT6h11W0d8pHuHV8AYz5N0r AOmyOe8NIY39t6G9qihPSvLdkuZXZ3oJmuVzrk/0ubYb8lIKwLgr6u3xRYwkdNUjcrOV Yyvjpk3cqBXKRz2VYznicd2TuyxK97QAYhqxFFoek9Ol3KhVpr2ol67IRPi91/m0nBVs zy3I1gc9kFMWCjfprA8dT/43h9NxfYdhUjn/gCO+swYN2psHaWPa85d6dJPUSwcec5tM C4+g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w17-v6si15445765pgk.497.2018.10.30.08.12.23; Tue, 30 Oct 2018 08:13:05 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727398AbeJaAE5 (ORCPT + 99 others); Tue, 30 Oct 2018 20:04:57 -0400 Received: from mga04.intel.com ([192.55.52.120]:35310 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727078AbeJaAE4 (ORCPT ); Tue, 30 Oct 2018 20:04:56 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Oct 2018 08:11:02 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,444,1534834800"; d="scan'208";a="86946152" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by orsmga006.jf.intel.com with ESMTP; 30 Oct 2018 08:11:02 -0700 Date: Tue, 30 Oct 2018 09:08:40 -0600 From: Keith Busch To: Jens Axboe Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner Subject: Re: [PATCH 11/14] irq: add support for allocating (and affinitizing) sets of IRQs Message-ID: <20181030150840.GC18906@localhost.localdomain> References: <20181029163738.10172-1-axboe@kernel.dk> <20181029163738.10172-12-axboe@kernel.dk> <20181030142601.GA18906@localhost.localdomain> <20181030144527.GB18906@localhost.localdomain> <46dbcbcd-799f-9970-a68f-de7e96b1a6bb@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46dbcbcd-799f-9970-a68f-de7e96b1a6bb@kernel.dk> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 30, 2018 at 08:53:37AM -0600, Jens Axboe wrote: > The sum of the set can't exceed the nvecs passed in, the nvecs passed in > should be the less than or equal to nvecs. Granted this isn't enforced, > and perhaps that should be the case. That should at least initially be true for a proper functioning driver. It's not enforced as you mentioned, but that's only related to the issue I'm referring to. The problem is pci_alloc_irq_vectors_affinity() takes a range, min_vecs and max_vecs, but a range of allowable vector allocations doesn't make sense when using sets.