On Wed, Mar 29, 2023 at 5:34 AM Bjorn Helgaas <helgaas@xxxxxxxxxx> wrote: > > "two params: on, off ... default param is NULL" doesn't read quite > right because "NULL" is not a valid parameter value. > > I think you could just omit that last sentence completely because it's > obvious that if you don't specify the parameter, it doesn't affect > anything and the existing behavior is unchanged (it's determined by > whether VMD_FEAT_CAN_BYPASS_MSI_REMAP is specified in vmd_ids[]). > Your opinion is more reasonable. I will omit this sentence. > > > Signed-off-by: Xinghui Li <korantli@xxxxxxxxxxx> > > Reviewed-by: Nirmal Patel <nirmal.patel@xxxxxxxxxxxxxxx> > > I think Lorenzo is out of the office this week, but I'm sure he'll > take care of this when he returns. > > In the meantime, can you include a sample usage in the commit log so > folks don't have to dig through the patch and figure out how to use > the parameter? > I will add instructions on how to use this parameter. > > It would also be nice to include a hint about why a user would choose > "on" or "off". What is the performance effect? What sort of I/O > scenario would lead you to choose "on" vs "off"? > Before this patch, I sent the patch named : PCI: vmd: Do not disable MSI-X remapping in VMD 28C0 controller (patchwork link: https://patchwork.kernel.org/project/linux-pci/patch/20221222072603.1175248-1-korantwork@xxxxxxxxx/) We found the 4k rand read's iops could drop 50% if 4 NVMEs were mounted in one PCIE port with VMD MSI bypass. I suppose this is because the VMD Controller can aggregate interrupts. But those test result is so long that I didn't add them to this patch commit log. If you believe it is necessary, I will try to add some simple instructions > > ee81ee84f873 ("PCI: vmd: Disable MSI-X remapping when possible") > suggests that MSI-X remapping (I assume the "msi_remap=on" case): > > - Limits the number MSI-X vectors available to child devices to the > number of VMD MSI-X vectors. > > - Reduces interrupt handling performance because child device > interrupts have to go through the VMD MSI-X domain interrupt > handler. > > So I assume "msi_remap=off" would remove that MSI-X vector limit and > improve interrupt handling performance? > > But obviously there's more to consider because those are both good > things and if we could do that all the time, we would. So there must > be cases where we *have* to remap. ee81ee84f873 suggests that not all > VMD devices support disabling remap. There's also a hint that some > virt configs require it. > I used to just want to disable 28C0's VMD MSI bypass by default. But Nirmal suggested the current method by adjusting the param. Because he and other reviewers worry there are some other scenarios we didn't consider. Adding a method to adjust VMD'S MSI-X mode is better. > This patch doesn't enforce either of those things. What happens if > the user gets it wrong? > If I am wrong, please feel free to correct me at any time. I place the "vmd_config_msi_remap_param" that is VMD MSI-X's mode param configuring helper front "vmd_enable_domain". So, It will not change the logic disabling remapping from ee81ee84f873, such as "Currently MSI remapping must be enabled in guest passthrough mode". So, if the user config the wrong type, it will not work, and they can find it by dmesg. And that's why I add the MSI-X mode init print. > > Spurious blank line. sorry for this > > > ee81ee84f873 mentions MSI-X explicitly (which is different from MSI), > so maybe use "MSI-X" here and in the messages below to avoid any > confusion. > That's nicer. > > The usual strcmp() idiom is to test "!strcmp(...)" instead of > "strcmp(...) == 0)". No need for "()" around > VMD_FEAT_CAN_BYPASS_MSI_REMAP. > All right, I will change it to "!strcmp()" way. Thanks for you review~
