On Wed, May 11, 2016 at 11:25:59AM -0700, Stephen Hemminger wrote: > On Wed, 11 May 2016 22:32:16 +0530 > Jerin Jacob <jerin.jacob at caviumnetworks.com> wrote: > > > On Wed, May 11, 2016 at 08:22:59AM -0700, Stephen Hemminger wrote: > > > On Wed, 11 May 2016 19:17:58 +0530 > > > Hemant Agrawal <hemant.agrawal at nxp.com> wrote: > > > > > > > IGB_UIO not supported for arm64 arch in kernel so disable. > > > > > > > > Signed-off-by: Hemant Agrawal <hemant.agrawal at nxp.com> > > > > Reviewed-by: Santosh Shukla <santosh.shukla at caviumnetworks.com> > > > > > > Really, I have use IGB_UIO on ARM64 > > > > May I know what is the technical use case for igb_uio on arm64 > > which cannot be addressed through vfio or vfioionommu. > > I was running on older kernel which did not support vfioionommu mode.
That way if we see older and latest kernel does not have ibg_uio(due to sysfs mmap issue) support .If you are back-porting the changes I recommend to back port vfioionommu changes to old kernel. If it comes to out of tree then dpdk out of tree configuration can also set CONFIG_RTE_EAL_IGB_UIO or even while configuring dpdk. IMO, It is better to keep arm64 dpdk.org changes inline with upstream arm64 linux kernel changes. What do you think?
