> -----Original Message----- > From: Yigit, Ferruh > Sent: Tuesday, June 27, 2017 12:36 PM > > For 2, does the "use existing methods" include calling xstats? If so, > > then we can just drop the requirement for 2 to have any new functions > > implemented in the driver. Instead, have the information provided by > > drivers in the normal xstats call, but have a new ethdev API to > > provide that information to the app - basically hiding the xstats > > complexity underneath. > > I was thinking another dev_ops similar to xstats, but re-using xstats can be > better idea here. > > so option 2 becomes: > [2] An eth_dev API to use existing APIs to get information from PMDs and > wrap MIBs related xstats calls. >
Instead of getting information/configuration related mib attributes in xstats_get, we should have new eth_dev op to get all those mib attributes which don’t have any ethdev API. Then the new eth_dev API can call this new eth_dev op and other existing ethdev APIs to gather all mib information and expose that to user. Thanks, Reshma
