> -----Original Message----- > From: Jerin Jacob [mailto:[email protected]] > Sent: Friday, September 28, 2018 4:46 PM > To: Rao, Nikhil <[email protected]> > Cc: Pavan Nikhilesh <[email protected]>; Van Haaren, > Harry <[email protected]>; [email protected]; > [email protected] > Subject: Re: [PATCH v2] examples/eventdev_pipeline: add Tx adapter support > > -----Original Message----- > > Date: Wed, 26 Sep 2018 18:26:37 +0530 > > From: "Rao, Nikhil" <[email protected]> > > To: Pavan Nikhilesh <[email protected]>, > > [email protected], [email protected], > > [email protected] > > CC: [email protected], "Rao, Nikhil" <[email protected]> > > Subject: Re: [PATCH v2] examples/eventdev_pipeline: add Tx adapter > > support > > User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) > > Gecko/20100101 > > Thunderbird/60.0 > > > > On 9/24/2018 3:42 PM, Pavan Nikhilesh wrote: > > > Redo the worker pipelines and offload transmission to service cores > > > seamlessly through Tx adapter. > > > > > > Signed-off-by: Pavan Nikhilesh <[email protected]> > > > --- > > > v2 Changes: > > > - Updated enqueue,dequeue depth thresholds. > > > - remove redundant capability checks. > > > > Reviewed-by: Nikhil Rao <[email protected]> > > Tested-by: Nikhil Rao <[email protected]> > > > Applied to dpdk-next-eventdev/master. Thanks. > Hi Pavan,
A couple of questions: 1. For the generic pipeline case with the SW PMD, the tx adapter port's default dequeue depth value causes performance regression from ~12 mpps to 7mpps. While the -c command line argument is also applicable to the tx adapter's port, since packet flow to the tx adapter port is of a different nature than the worker ports, how about adding the dequeue depth for the tx adapter port as a separate command line argument with a default value of 128 ? 2. -n parameter and stats for the generic pipeline that were available in the app previously do not work, do you plan to add this functionality ? Thanks, Nikhil
