Re: [dpdk-dev] [PATCH v5 2/2] eal/vfio: export internal vfio functions

Thu, 05 Apr 2018 04:02:15 -0700 

Yes, it's private. We could do that if really needed.

BRs,
Xiao
> -----Original Message-----
> From: Thomas Monjalon [mailto:[email protected]]
> Sent: Thursday, April 5, 2018 6:23 PM
> To: Wang, Xiao W <[email protected]>
> Cc: Hemant Agrawal <[email protected]>; [email protected]; Burakov,
> Anatoly <[email protected]>
> Subject: Re: [dpdk-dev] [PATCH v5 2/2] eal/vfio: export internal vfio 
> functions
> 
> 05/04/2018 11:03, Wang, Xiao W:
> 
> > > +int rte_vfio_get_group_num(const char *sysfs_base, const char
> *dev_addr,
> > > +                    int *iommu_group_num);
> > > +int rte_vfio_get_container_fd(void);
> > > +int rte_vfio_get_group_fd(int iommu_group_num);
> >
> > Considering the "group_no" field defined in eal_vfio.h, will
> "iommu_group_num" cause inconsistency
> > In naming?
> 
> I asked to change the function name to "num" because it is more meaningful.
> "group_no" field is private? Can it be renamed?
>

Reply via email to