On Thu, Mar 25, 2021 at 1:01 AM McDaniel, Timothy <[email protected]> wrote: > > > > > -----Original Message----- > > From: Jerin Jacob <[email protected]> > > Sent: Sunday, March 21, 2021 4:48 AM > > To: McDaniel, Timothy <[email protected]> > > Cc: dpdk-dev <[email protected]>; Jerin Jacob <[email protected]>; Van Haaren, > > Harry <[email protected]>; Ray Kinsella <[email protected]>; Neil > > Horman <[email protected]>; Rao, Nikhil <[email protected]>; > > Carrillo, Erik G <[email protected]>; Gujjar, Abhinandan S > > <[email protected]>; Pavan Nikhilesh > > <[email protected]>; Hemant Agrawal <[email protected]>; > > mattias.ronnblom <[email protected]>; Mccarthy, Peter > > <[email protected]> > > Subject: Re: [dpdk-dev] [PATCH 01/25] event/dlb2: add dlb v2.5 probe > > > > On Wed, Mar 17, 2021 at 3:49 AM Timothy McDaniel > > <[email protected]> wrote: > > > > > > This commit adds dlb v2.5 probe support, and updates > > > parameter parsing. > > > > > > The dlb v2.5 device differs from dlb v2, in that the > > > number of resources (ports, queues, ...) is different, > > > so macros have been added to take the device version > > > into account. > > > > > > This commit also cleans up a few issues in the original > > > dlb2 source: > > > - eliminate duplicate constant definitions > > > - removed unused constant definitions > > > > > > Signed-off-by: Timothy McDaniel <[email protected]> > > > --- > > > > > > > > -#define EVDEV_DLB2_NAME_PMD dlb2_event > > > +#define EVDEV_DLB2_NAME_PMD dlb_event > > > > Is this an intended change? why change the driver's name. > > Yes, This is an intentional change. We will be using the same driver name > going forward, regardless of the hardware version. > Internally, we know which version of the hardware is present.
Since the driver name is still driver/event/dlb2. Keep it as same prefix scheme with other drivers. > > Thanks, > Tim >
