Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 732E2C05027 for ; Tue, 7 Feb 2023 03:17:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229792AbjBGDRt (ORCPT ); Mon, 6 Feb 2023 22:17:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35002 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229656AbjBGDRl (ORCPT ); Mon, 6 Feb 2023 22:17:41 -0500 Received: from mail-pg1-x544.google.com (mail-pg1-x544.google.com [IPv6:2607:f8b0:4864:20::544]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DC94A6EB4; Mon, 6 Feb 2023 19:17:18 -0800 (PST) Received: by mail-pg1-x544.google.com with SMTP id s8so7476849pgg.11; Mon, 06 Feb 2023 19:17:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=gEdx9HDblWu1Giy1hcfGtLMQdifTw+HkdbmqOyodOVw=; b=ZQguRZWuUDg7ejfZ/13IUqBONLkGw/N7iaWg0B8vANmtG84iFjPnY6fM1T5sxuvWr4 BVXFn6dpf0dSLPAoIYvSchUqB8uw7ldaR5AZm6NwPimviECDkBFkBm6pQa2095BxMH92 OwNggtDAhapuz3RfH2ox88YncBCOeggM6qJQBO0EK58MjVlFx+gHpgXQvOM5/e3qiOvx 5hzyq46Q4AcvttjGTckqq9ZvzwOrSUI8nxEDPt4S7GdqHyPvcMjJj8v8dR98M6bCFQjh rVRusBUsoQJCJLQPhRneG4bZoWWGE50xquMq99QwVcRPcbqhAFpgf79Yz3cGuuxHb1bk G6uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=gEdx9HDblWu1Giy1hcfGtLMQdifTw+HkdbmqOyodOVw=; b=YDzSoI6NccQxB2MGZxnXemr16HjSbmPoHbJak2Wgz8zpobJKN5jLyOxxa0H9/+as3a xnxQombb+2QNN05Mmw2y29k9OpE4L8fFtMeGvnXUlAtVbkmioJTjyooZfAGX21USoUTU pwhlBloEi27XLtkWonNPSFAc07QnQcnxyHP2ZsUA5CgSjDdp3v6avE0Bs7oRlhCfBDtY 8OVl7yxns9PV5Zq24rPsCIdjaJHimCV+XXlQoeVAKP/ClzMl14LE0hZJciGTH4mXjLYQ NVqH+oP/dntf3yM2h7Da+Gp4EPZ+a+4KNpjeS1IFdtUTkn0x8pt2edBB09rMn3fKUYTA 6+/w== X-Gm-Message-State: AO0yUKWYAvRbndCNQKPaYKIPpZObzjICuVRgcaFDQayjUcZ7nTYuRLuJ gI001Po5ac5JWN+by0B3h7G87DRZidnF6DufcH0= X-Google-Smtp-Source: AK7set/IgnWvC+1T7ik0Cn8q8NqR2wk3vROsEsFNmbgUQDJ+HPmjizDorws0xZCeIry6U0mHESWMMzbsaq+75SD8HP4= X-Received: by 2002:a62:2506:0:b0:5a7:2295:cb03 with SMTP id l6-20020a622506000000b005a72295cb03mr330917pfl.18.1675739838359; Mon, 06 Feb 2023 19:17:18 -0800 (PST) MIME-Version: 1.0 References: <20221222072603.1175248-1-korantwork@gmail.com> <3d1834d9-7905-1225-741a-f298dd5b8a8e@linux.dev> <9e6cfda1-4309-d1bb-a0cf-404a7fe7d3aa@linux.intel.com> In-Reply-To: From: Xinghui Li Date: Tue, 7 Feb 2023 11:18:14 +0800 Message-ID: Subject: Re: [PATCH] PCI: vmd: Do not disable MSI-X remapping in VMD 28C0 controller To: Keith Busch Cc: "Patel, Nirmal" , Jonathan Derrick , lpieralisi@kernel.org, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, Xinghui Li Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Keith Busch =E4=BA=8E2023=E5=B9=B42=E6=9C=887=E6=97=A5= =E5=91=A8=E4=BA=8C 02:28=E5=86=99=E9=81=93=EF=BC=9A > > On Mon, Feb 06, 2023 at 11:11:36AM -0700, Patel, Nirmal wrote: > > I like the idea of module parameter to allow switching between the mode= s > > but keep MSI remapping enabled (non-bypass) by default. > > Isn't there a more programatic way to go about selecting the best option = at > runtime? Do you mean that the operating mode is automatically selected by detecting the number of devices and CPUs instead of being set manually? >I suspect bypass is the better choice if "num_active_cpus() > pci_msix_vec= _count(vmd->dev)". For this situation, My speculation is that the PCIE nodes are over-mounted and not just because of the CPU to Drive ratio. We considered designing online nodes, because we were concerned that the IO of different chunk sizes would adapt to different MSI-X modes. I privately think that it may be logically complicated if programmatic judgments are made.