From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <rkerur@gmail.com> Received: from mail-pg0-f48.google.com (mail-pg0-f48.google.com [74.125.83.48]) by dpdk.org (Postfix) with ESMTP id 121BB282 for <dev@dpdk.org>; Thu, 11 May 2017 03:51:57 +0200 (CEST) Received: by mail-pg0-f48.google.com with SMTP id o3so6478169pgn.2 for <dev@dpdk.org>; Wed, 10 May 2017 18:51:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=z3bD4x5GSZVWUUMFZ86AwCGMoxoPFGDeML9PVaGg+Fo=; b=l4PChMSpvfNVbhkPakfx0a8vI7hhtBL8hNVo2Zm4yTUBRSnoCfLXVZzPp7FjJq0ACz 3mlkanqX5hqWZOKpMQm6PijC6s+wdtdUHM+1Bt2gYwMlGC01w55Od5RyRzSDq02FsAzO F9x7JUKiWKGAd/RsL7/nx8UVCGC70bWcECZBkfgFrT8Jfcf7RexfZj1disH+oZXOb/GT +T2arPjhN4WpT/aqCzGZpBDlrvZJ3UzIcMpcKOX+6Byw9x1HIJMmxyr0ECDbtAz8hC8W NA+bfHj6cmdz90/T3ayfhKhQY3m6H+d9k/DgxyqJlx77+F5bVLs50WLk8dGu761x/xvJ 8lWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=z3bD4x5GSZVWUUMFZ86AwCGMoxoPFGDeML9PVaGg+Fo=; b=J6WR6BNuT+Xr3BJOfA5dQNnFwUG3OEJoEw/aLX5asM/ek8uygJt9Zbu47yUNawsX6k kGIn4NZip626NTHmcNPwDjTcOsBJRAr1+UHklWn6pcS7lOjMh6Xtx73KfJJGy93JrQyC w1ea9E8sEqgmcpl8KHsCglWib5LihVH0br7//WTjvLi/i5piARpfR5BWdUG7jwI4XB+o wmK5kWmfjGF5VblMUO0Bj12FS94myryiPidf2G+6OnAcNbGHcHFri/5KuIPx3pk1SSBn nW65QvIyE4bwKZdSQ2sZrriIeE8QY5Eoscp4cTb2DyILrkf/MyzfJN7kseeDcP843i2b vA/A== X-Gm-Message-State: AODbwcCOEAuG8/NdAMOAaSvzr2ltLAo5hIWZkq6KkTzxwmufgDVfrnJt KgzGozKZbLiN1bPWMeZaLQOWTHt6Nw== X-Received: by 10.99.174.75 with SMTP id e11mr9792952pgp.177.1494467516323; Wed, 10 May 2017 18:51:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.180.42 with HTTP; Wed, 10 May 2017 18:51:55 -0700 (PDT) In-Reply-To: <B27915DBBA3421428155699D51E4CFE2332CADEC@IRSMSX103.ger.corp.intel.com> References: <1493145557-17160-1-git-send-email-rkerur@gmail.com> <1494277227-25876-1-git-send-email-rkerur@gmail.com> <B27915DBBA3421428155699D51E4CFE2332CADEC@IRSMSX103.ger.corp.intel.com> From: Ravi Kerur <rkerur@gmail.com> Date: Wed, 10 May 2017 18:51:55 -0700 Message-ID: <CAFb4SLDFd2=JBLvjnVtwGXG7fOx0-1O7J3p0aAxPFgHCgJpAKw@mail.gmail.com> To: "Mcnamara, John" <john.mcnamara@intel.com> Cc: "dev@dpdk.org" <dev@dpdk.org>, "thomas@monjalon.net" <thomas@monjalon.net> Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH v2] doc: Merge l3fwd and l3fwd-acl documentation files X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list 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> X-List-Received-Date: Thu, 11 May 2017 01:51:57 -0000 On Wed, May 10, 2017 at 3:14 AM, Mcnamara, John <john.mcnamara@intel.com> wrote: > > > > -----Original Message----- > > From: Ravi Kerur [mailto:rkerur@gmail.com] > > Sent: Monday, May 8, 2017 10:00 PM > > To: dev@dpdk.org > > Cc: Mcnamara, John <john.mcnamara@intel.com>; thomas@monjalon.net; Ravi > > Kerur <rkerur@gmail.com> > > Subject: [PATCH v2] doc: Merge l3fwd and l3fwd-acl documentation files > > > > Merge l3fwd and l3fwd-acl documentation to reflect the code. > > Add examples of LPM and Exact Match rules in .svg files. > > > > Signed-off-by: Ravi Kerur <rkerur@gmail.com> > > --- > > v2: > > Remove binary PNG from .svg files. > > > > v1: > > Merge relevant contents of l3fwd and l3fwd-acl documentation. > > Modify l3fwd document with ACL specific information. > > Remove l3fwd-acl documentation file. > > --- > > doc/guides/sample_app_ug/img/ipv4_hash_rule.svg | 108 ++++++ > > doc/guides/sample_app_ug/img/ipv4_lpm_rule.svg | 96 +++++ > > doc/guides/sample_app_ug/index.rst | 1 - > > doc/guides/sample_app_ug/l3_forward.rst | 326 > > ++++++++++++++++- > > .../sample_app_ug/l3_forward_access_ctrl.rst | 385 > ---------------- > > ----- > > 5 files changed, 521 insertions(+), 395 deletions(-) create mode 100644 > > doc/guides/sample_app_ug/img/ipv4_hash_rule.svg > > create mode 100644 doc/guides/sample_app_ug/img/ipv4_lpm_rule.svg > > > > > Thanks once more for the doc. Some comments below. > > > > ... > > Redistribution and use in source and binary forms, with or without > @@ > > -31,12 +31,18 @@ > > L3 Forwarding Sample Application > > ================================ > > > > -The L3 Forwarding application is a simple example of packet processing > > using the DPDK. > > -The application performs L3 forwarding. > > +The L3 Forwarding with Hash, LPM or Access Control application is a > > simple example of packet processing using the DPDK. > > +The application performs L3 forwarding when Hash or LPM is used. > > +The application performs a security check on received packets when > Access > > Control is used. > > +Packets that are in the Access Control List (ACL), which is loaded > during > > initialization, are dropped. > > +Others are forwarded to the correct port. > > > For the introduction I would suggest the following rewording: > > L3 Forwarding Sample Application > ================================ > > The L3 Forwarding application is a simple example of packet processing > using > the DPDK with Hash, LPM (Longest Prefix match) or Access Control. > > The application performs L3 forwarding when Hash or LPM is used. > Alternatively, the application performs a security check on received > packets > when Access Control is used. Packets that are in the Access Control List > (ACL), which is loaded during initialization, are dropped. Others packets > are > forwarded to the correct port. > > > > > > The main difference from the L2 Forwarding sample application is that > the > > forwarding decision @@ -49,15 +55,263 @@ The hash object is used in > > correlation with a flow table to map each input packe The hash lookup > key > > is represented by a DiffServ 5-tuple composed of the following fields > read > > from the input packet: > > Source IP Address, Destination IP Address, Protocol, Source Port and > > Destination Port. > > This is fine but would be a bit clearer as a list: > > > The hash lookup key is represented by a 5-tuple composed of the following > fields read from the input packet: > > * Source IP Address. > * Destination IP Address. > * Protocol. > * Source Port. > * Destination Port. > > > > > + > > +.. _figure_ipv4_lpm_rule: > > + > > +.. figure:: img/ipv4_lpm_rule.* > > + > > + A typical IPv4 LPM rule > > + > > +* A typical IPv4 hash rule line should have a format as shown below: > > + > > + > > +.. _figure_ipv4_hash_rule: > > + > > +.. figure:: img/ipv4_hash_rule.* > > + > > + A typical IPv4 hash rule > > + > > > Unfortunately these figures don't render very well. I would suggest > replacing > them with text, like below: > > > A typical IPv4 LPM rule line in an input file would look like the > following:: > > > # Dest Address/mask Eth port > # ================= ======== > > L100.10.10.10/24 0 > > > A typical IPv4 Hash rule line in an input file would look like the > following:: > > # Src Address Dst Address Src Port Dst port Protocol Eth port > # =========== =========== ======== ======== ======== ======== > > E100.10.10.0 100.10.0.0 110 111 0x6 0 > > > There a few other thing that could be improved in the doc but these issues > were > already there in text that you are merging so apart from these suggestion > the rest of the doc is okay for now. We should try to come back and improve > the consistency at a later date. > > Thanks John. Sent a 'v3' with your inputs incorporated. > John > > > > >