I have pushed another patch addressing David's comments.
https://patches.dpdk.org/project/dpdk/patch/20231113172759.3529518-1-abdullah.sevin...@intel.com/
>+Ok, that is indeed an issue.
>+I found some patches exposing this capability with vfio-pci but I am not sure
>what is the latest work on the topic.
That's right, some kernels may expose the capability some not. We realized it
when Bruce reported my earlier patch with the api rte_pci_find_ext_
Hello,
On Mon, Nov 6, 2023 at 7:50 PM Sevincer, Abdullah
wrote:
> Hi David,
> >++ pasid_offset = rte_pci_find_ext_capability(dev,
> >+RTE_PCI_EXT_CAP_ID_PASID);
>
> That rte_pci_find_ext_capability() api does not work for PASID since PASID
> is not exposed to user from kernel.
> So, we ca
>+I don't see much point in providing a wrapper that does nothing more than
>call rte_pci_write_config() and let the driver pass the right offsets.
>+If anything, can't this wrapper find out about the pasid offset itself?
>+There is a extended capability for this, so I would expect it can be use
On Mon, Nov 6, 2023 at 6:05 PM Abdullah Sevincer
wrote:
>
> Add an internal API to control PASID for a given PCIe device.
>
> For kernels when PASID enabled by default it breaks DLB functionality,
> hence disabling PASID is required for DLB to function properly.
>
> PASID capability is not exposed
5 matches
Mail list logo
