From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f178.google.com (mail-we0-f178.google.com [74.125.82.178]) by dpdk.org (Postfix) with ESMTP id E162F5A03 for ; Thu, 19 Mar 2015 12:24:08 +0100 (CET) Received: by weop45 with SMTP id p45so54593120weo.0 for ; Thu, 19 Mar 2015 04:24:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references; bh=CGfn5Hq9UEOxb/ZSo7mYlTehJf1DE0h6HqFkhRaCh3Y=; b=jL1ZJ0d2ZW0mrSkO9QxtFo5h/JUuFBQqdHEXC4EffQejsA9L2SUiWJPKhbW/5kaVgv bqQIuhuKlVJxtN9oJwr72xwT3G7dsij589JL8q5EEe0i+jIa8tjNfsV0ghq9bXorjdq/ 8yB+OI8Ve2xv1DEI1mtPlnWDReuutMmzkmY0TorkXgCIUzJtH8CtQ+DX6coQR0n2fw7P gwz7ofgO46fHVKjwvdKr3DoHu84W949P66dJua3n5f/xxHKot8vMfD0L9JRjwijEx60t xsqoxKHgYa4+VDDTI9ss11ylJCrX5oIaLbCYa9M7XI/H66RQ20cCzav090ZVF69gf7q/ +TnQ== X-Gm-Message-State: ALoCoQm8jtbuwBmO7K+58l/mGpb02gI9I7aGMNpJIzZSfmtZoDHROSSgYj7O7NZUrV+ioQ58ggcW X-Received: by 10.194.8.99 with SMTP id q3mr154692381wja.88.1426764248702; Thu, 19 Mar 2015 04:24:08 -0700 (PDT) Received: from localhost.localdomain (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id y14sm1537682wjr.39.2015.03.19.04.24.07 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 19 Mar 2015 04:24:08 -0700 (PDT) From: Thomas Monjalon To: john.mcnamara@intel.com Date: Thu, 19 Mar 2015 12:23:19 +0100 Message-Id: <1426764204-3882-3-git-send-email-thomas.monjalon@6wind.com> X-Mailer: git-send-email 2.2.2 In-Reply-To: <1426764204-3882-1-git-send-email-thomas.monjalon@6wind.com> References: <1422972678-7982-1-git-send-email-john.mcnamara@intel.com> <1426764204-3882-1-git-send-email-thomas.monjalon@6wind.com> Cc: dev@dpdk.org Subject: [dpdk-dev] [PATCH v5 2/7] doc: refactor split cell formatting in table X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Mar 2015 11:24:09 -0000 From: John McNamara Refactored split cell in test_pipeline table to allow it to convert cleanly to PDF. The Sphinx/Latex converter doesn't handle split cells like the following: +-------------+--------------+ | Header 1 | Header 2 | +=============+==============+ | | | | | | +-------------+ | | | | | | | +-------------+--------------+ Instead the table was refactored to a simpler format: +-------------+--------------+ | Header 1 | Header 2 | +=============+==============+ | | | | | | +-------------+--------------+ | | | | | | +-------------+--------------+ The same information was retained in the table. Signed-off-by: John McNamara Acked-by: Bernard Iremonger --- doc/guides/sample_app_ug/test_pipeline.rst | 32 ++++++++++++++++++++---------- 1 file changed, 22 insertions(+), 10 deletions(-) diff --git a/doc/guides/sample_app_ug/test_pipeline.rst b/doc/guides/sample_app_ug/test_pipeline.rst index 867a7a7..a5fed8a 100644 --- a/doc/guides/sample_app_ug/test_pipeline.rst +++ b/doc/guides/sample_app_ug/test_pipeline.rst @@ -137,9 +137,9 @@ For hash tables, the following parameters can be selected: | | | entries. | hash table with the following key format: | | | | | | | | | | [4-byte index, 4 bytes of 0] | -+-------+------------------------+----------------------------------------------------------+ | -| 4 | hash-[spec]-8-ext | Extendible bucket hash table with 8-byte key size | The action configured for all table entries is | -| | | and 16 million entries. | "Sendto output port", with the output port index | +| | | | | +| | | | The action configured for all table entries is | +| | | | "Sendto output port", with the output port index | | | | | uniformly distributed for the range of output ports. | | | | | | | | | | The default table rule (used in the case of a lookup | @@ -152,13 +152,17 @@ For hash tables, the following parameters can be selected: | | | | [destination IPv4 address, 4 bytes of 0] | | | | | | +-------+------------------------+----------------------------------------------------------+-------------------------------------------------------+ +| 4 | hash-[spec]-8-ext | Extendible bucket hash table with 8-byte key size | Same as hash-[spec]-8-lru table entries, above. | +| | | and 16 million entries. | | +| | | | | ++-------+------------------------+----------------------------------------------------------+-------------------------------------------------------+ | 5 | hash-[spec]-16-lru | LRU hash table with 16-byte key size and 16 million | 16 million entries are successfully added to the hash | | | | entries. | table with the following key format: | | | | | | | | | | [4-byte index, 12 bytes of 0] | -+-------+------------------------+----------------------------------------------------------+ | -| 6 | hash-[spec]-ash-16-ext | Extendible bucket hash table with 16-byte key size | The action configured for all table entries is | -| | | and 16 million entries. | "Send to output port", with the output port index | +| | | | | +| | | | The action configured for all table entries is | +| | | | "Send to output port", with the output port index | | | | | uniformly distributed for the range of output ports. | | | | | | | | | | The default table rule (used in the case of a lookup | @@ -171,13 +175,17 @@ For hash tables, the following parameters can be selected: | | | | [destination IPv4 address, 12 bytes of 0] | | | | | | +-------+------------------------+----------------------------------------------------------+-------------------------------------------------------+ +| 6 | hash-[spec]-16-ext | Extendible bucket hash table with 16-byte key size | Same as hash-[spec]-16-lru table entries, above. | +| | | and 16 million entries. | | +| | | | | ++-------+------------------------+----------------------------------------------------------+-------------------------------------------------------+ | 7 | hash-[spec]-32-lru | LRU hash table with 32-byte key size and 16 million | 16 million entries are successfully added to the hash | -| | | entries. | table with the following key format: | +| | | entries. | table with the following key format: | | | | | | | | | | [4-byte index, 28 bytes of 0]. | -+-------+------------------------+----------------------------------------------------------+ | -| 8 | hash-[spec]-32-ext | Extendible bucket hash table with 32-byte key size | The action configured for all table entries is | -| | | and 16 million entries. | "Send to output port", with the output port index | +| | | | | +| | | | The action configured for all table entries is | +| | | | "Send to output port", with the output port index | | | | | uniformly distributed for the range of output ports. | | | | | | | | | | The default table rule (used in the case of a lookup | @@ -190,6 +198,10 @@ For hash tables, the following parameters can be selected: | | | | [destination IPv4 address, 28 bytes of 0] | | | | | | +-------+------------------------+----------------------------------------------------------+-------------------------------------------------------+ +| 8 | hash-[spec]-32-ext | Extendible bucket hash table with 32-byte key size | Same as hash-[spec]-32-lru table entries, above. | +| | | and 16 million entries. | | +| | | | | ++-------+------------------------+----------------------------------------------------------+-------------------------------------------------------+ | 9 | lpm | Longest Prefix Match (LPM) IPv4 table. | In the case of two ports, two routes | | | | | are added to the table: | | | | | | -- 2.2.2