Hi John, On Thu, Mar 9, 2017 at 2:23 AM, Mcnamara, John <john.mcnam...@intel.com> wrote:
> > From: Ravi Kerur [mailto:rke...@gmail.com] > > Sent: Monday, March 6, 2017 11:21 PM > > To: Mcnamara, John <john.mcnam...@intel.com> > > Cc: dev@dpdk.org; Ananyev, Konstantin <konstantin.anan...@intel.com>; > > Richardson, Bruce <bruce.richard...@intel.com> > > Subject: Re: [dpdk-dev] [v4 0/3] Merge l3fwd-acl and l3fwd > > > > > > Should I work with documentation team to update the document? If yes, > > please let me know the contact information. > > Hi Ravi, > > There isn't any documentation team. Unfortunately. :-) > > The raw documentation is in text format and is generally updated by > the developer submitting a patch. > > There is already docs for l3fwd and l3fwd_acl so all that is required > is to merge them. However, you will need to take some care to remove > the duplicate sections and to make sure that the merged doc makes > sense as a whole. > > See the documentation guidelines: > > http://dpdk.org/doc/guides/contributing/documentation.html Thanks. I realized after skimming through the documents and seeing a 'doc:' prefix for review. Some clarifications on merging 'l3fwd' and 'l3fwd-acl' 1. Instead of wholesale merger of both 'l3fwd' and 'l3fwd-acl', does it make sense to a. Modify 'l3fwd' document by adding ACL processing information ('-A' cmdline) and providing a link or reference to existing 'l3fwd-acl' documentation since nothing has changed in terms of 'l3fwd-acl'. b. Add file read options for 'exact match' and 'longest prefix match' in 'l3fwd' documentation. Thanks. > > > John >
