From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ravi Kerur <rkerur@gmail.com>
Subject: Re: [v4 0/3] Merge l3fwd-acl and l3fwd
Date: Tue, 14 Mar 2017 14:14:12 -0700
Message-ID: <CAFb4SLD-9xuYRXiJmGNm8++bSTmBHe0v=TMTj=X-bC7ASLCHcw@mail.gmail.com>
References: <1488743225-25750-1-git-send-email-rkerur@gmail.com>
 <B27915DBBA3421428155699D51E4CFE23324F7B2@IRSMSX104.ger.corp.intel.com>
 <CAFb4SLAmkAuLvnBJy9QSZkR56+HiGwydWdVw_h1dWdLtJr9OAQ@mail.gmail.com>
 <B27915DBBA3421428155699D51E4CFE233256795@IRSMSX104.ger.corp.intel.com>
 <CAFb4SLDskNztBEUSWQO4fGotmU3rJoggUV8A5YYL9qMas6xs2w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Ananyev,
 Konstantin" <konstantin.ananyev@intel.com>,
 "Richardson, Bruce" <bruce.richardson@intel.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pf0-f174.google.com (mail-pf0-f174.google.com
 [209.85.192.174]) by dpdk.org (Postfix) with ESMTP id E6E752C74
 for <dev@dpdk.org>; Tue, 14 Mar 2017 22:14:13 +0100 (CET)
Received: by mail-pf0-f174.google.com with SMTP id o126so75675781pfb.3
 for <dev@dpdk.org>; Tue, 14 Mar 2017 14:14:13 -0700 (PDT)
In-Reply-To: <CAFb4SLDskNztBEUSWQO4fGotmU3rJoggUV8A5YYL9qMas6xs2w@mail.gmail.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi John, Konstantin,

On Thu, Mar 9, 2017 at 4:07 PM, Ravi Kerur <rkerur@gmail.com> wrote:

> Hi John,
>
> On Thu, Mar 9, 2017 at 2:23 AM, Mcnamara, John <john.mcnamara@intel.com>
> wrote:
>
>> > From: Ravi Kerur [mailto:rkerur@gmail.com]
>> > Sent: Monday, March 6, 2017 11:21 PM
>> > To: Mcnamara, John <john.mcnamara@intel.com>
>> > Cc: dev@dpdk.org; Ananyev, Konstantin <konstantin.ananyev@intel.com>;
>> >     Richardson, Bruce <bruce.richardson@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.
>

Kindly let me know how you want me to proceed with the changes to
documentation?

Thanks.


>
>  Thanks.
>
>>
>>
>> John
>>
>
>