From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sipsolutions.net (s3.sipsolutions.net [168.119.38.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 394C2371893; Fri, 20 Mar 2026 08:28:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=168.119.38.16 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773995337; cv=none; b=dQNAEdLmBzBFEfm4QRMDzRreV1dXMg5RG5i1DBipEM7LLHMgciGxixSWGXWK3x922tL6O/3xBOdJx8m316lIpKYYD8UaIcSma5qBVj4t/UrWsKDEFPU3So342/sCm6U+DQTBFTeKymQcUMuEKnBKV5OeHzV/ffV6BGMRZrpSSOc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773995337; c=relaxed/simple; bh=6uDVse/f+UqXumUFSeU6eMXonNr+xu2lqIdDrA6J69I=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:MIME-Version; b=azOclOIsx3C4e2hfCHPebJlrsNGCCswkPs0zXksxYHaKcxbPf63Gvk97lZV9RGbmZUSKPcPPhhEWqmDe0coK04BLN0SY0dTEXl7BLxgV8r6XLmfwVWwib9tck5AhFFjO3mSmtufuSK5Cs9cM4tXxPHbI/ZQk4ahqmin0YnXCbAs= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net; spf=pass smtp.mailfrom=sipsolutions.net; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b=PguadrS3; arc=none smtp.client-ip=168.119.38.16 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sipsolutions.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sipsolutions.net header.i=@sipsolutions.net header.b="PguadrS3" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=MIME-Version:Content-Transfer-Encoding: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=6uDVse/f+UqXumUFSeU6eMXonNr+xu2lqIdDrA6J69I=; t=1773995336; x=1775204936; b=PguadrS3HACIwgsKg3kiS+Y3RfMtUtI0jZT8PvYrvdrAehI XfIca47MyQW7kaHHkZyR7SMR+YvsMXCierDgnGLSeoZeL9Do/va5dsOFZDAKCDc3s0OCFXzYXbS+P z3krldAq5CFsXOf+2m+JKohWMKOx3EktbJcyE/qi0vkzsy+EiRQwe+OtIJutt91JQxF4C1CW5FJDP nKNNioFYq3BuZK9fkQnM7DEjcjv5G5BnBt6fc3sV9KdX5r3YJYefMys03J9u0nxShSme2aPlbTIEo KiEsZJ0N9cYsUTQzNkBVZk4PqnT31BqEg9QUEstk5URHjMoTCCTLdt/TZopVZ6/Q==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_X25519__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.98.2) (envelope-from ) id 1w3VDx-00000006VMm-0MwK; Fri, 20 Mar 2026 09:28:53 +0100 Message-ID: <322b0d12d583dfac3f7d79dd1e4e22fcb413a946.camel@sipsolutions.net> Subject: Re: [PATCH v7 1/3] wifi: iwlwifi: pcie: migrate to modern pci_alloc_irq_vectors API From: Johannes Berg To: =?ISO-8859-1?Q?Adri=E1n_Garc=EDa?= Casado , Miri Korenblit Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, Miguel Ojeda Date: Fri, 20 Mar 2026 09:28:52 +0100 In-Reply-To: <20260319182925.19436-1-adriangarciacasado42@gmail.com> References: <20260319182925.19436-1-adriangarciacasado42@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-malware-bazaar: not-scanned Hi, So given your exchange with Miguel, I was not going to reply, but On Thu, 2026-03-19 at 19:29 +0100, Adri=C3=A1n Garc=C3=ADa Casado wrote: > Johannes Berg suggested using pci_alloc_irq_vectors() and delegating > affinity management to the kernel. I don't know where this came from, I never suggested that? I _did_ suggest that if this change is somehow necessary (which you've not convinced anyone of), the driver should allocate fewer queues rather than just spreading the same number of queues over fewer cores and double-booking one of the cores. Please take a step back, (re-)read all the feedback you've been given, figure out why you want this change, and come back with a coherent explanation and changes addressing feedback (or explanations why not.) johannes