[dpdk-dev] [PATCH 1/8] doc: add doc to explain compiling and testing of PMD

[Jerin Jacob]

-----Original Message-----
> Date: Fri, 7 Apr 2017 12:37:26 +0530
> From: Shijith Thotton <shijith.thotton at caviumnetworks.com>
> To: Thomas Monjalon <thomas.monjalon at 6wind.com>
> CC: John Mcnamara <john.mcnamara at intel.com>, dev at dpdk.org, Ferruh Yigit
>  <ferruh.yigit at intel.com>
> Subject: Re: [dpdk-dev] [PATCH 1/8] doc: add doc to explain compiling and
>  testing of PMD
> User-Agent: Mutt/1.5.21 (2010-09-15)
> 
> On Thu, Apr 06, 2017 at 08:30:21PM +0200, Thomas Monjalon wrote:
> > 2017-04-06 13:21, Shijith Thotton:
> > > Add a section in NIC drivers documentation to explain compiling and
> > > testing of a PMD. It also mentions about host setup, which is required
> > > before running testpmd.
> > > 
> > > Add label "testpmd_ug" to refer user guide.
> > > 
> > > Signed-off-by: Shijith Thotton <shijith.thotton at caviumnetworks.com>
> > 
> > It is really good to factorize documentation.
> > 
> > This doc is about testpmd in Linux
> > and does not refer to FreeBSD.
> > Do we assume to take Linux as the reference?
> 
> I can submit v2 with a subsection for running testpmd in FreeBSD.
> 
> > Should we refer to the Linux Getting Started Guide instead?
> 
> Agree that the new section just has steps from getting started guide. It may
> seem redundant from a developer point of view, but hope it will be useful to
> users.
> 
> Please share thoughts.

1) Some reason thunderx PMD is not added in refactoring. I guess its due
to x86 and arm64 name space collision in the common document, if so we need
to find a way to fix it and thunderx PMD.

2)I guess, It is better to keep all the startup logs in respective PMD.I
think, it will help in debugging in case there are any issues.


> 
> Thanks,
> Shijith