[dpdk-dev] [PATCH v6 3/8] eal/bsd: dummy for new intr definition

Liang, Cunming cunming.liang at intel.com
Sat Feb 28 01:37:24 CET 2015



> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Friday, February 27, 2015 10:22 PM
> To: Liang, Cunming
> Cc: David Marchand; dev at dpdk.org; Stephen Hemminger
> Subject: Re: [PATCH v6 3/8] eal/bsd: dummy for new intr definition
> 
> 2015-02-27 11:21, Liang, Cunming:
> > From: David Marchand [mailto:david.marchand at 6wind.com]
> > > On Fri, Feb 27, 2015 at 5:56 AM, Cunming Liang  wrote:
> > > > @@ -49,6 +51,8 @@ enum rte_intr_handle_type {
> > > >
> > > >  struct rte_intr_handle {
> > > >
> > > >         int fd;                          /**< file descriptor */
> > > >         enum rte_intr_handle_type type;  /**< handle type */
> > > >
> > > > +       int max_intr;                    /**< max interrupt requested */
> > > > +       uint32_t vec_num[VFIO_MAX_QUEUE_ID]; /**< rxtx intr vector
> number */
> > > > };
> > >
> > > No need to add those since this is not supported for bsd.
> >
> > [Liang, Cunming] max_intr is used in dev_init for pci_dev->intr_handle init.
> > Vec_num is used in ethdev API rx_intr_vec_get. Without it, BSD macro will
> > used for each of the reference place.
> > As they’re quite generic, even bsd will require either max_intr or vec
> > mapping table.
> 
> Is it needed to build and run DPDK on FreeBSD?
[LCM] As it's the EAL change, so I try to make sure FreeBSD can build and run as normal.



More information about the dev mailing list