DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: use correct IP reserved address range
Date: Tue, 5 Nov 2019 16:12:31 +0000	[thread overview]
Message-ID: <75e12b10-ebe0-e17d-799d-5d73956b85f2@intel.com> (raw)
In-Reply-To: <20191105160921.6951-1-stephen@networkplumber.org>

On 11/5/2019 4:09 PM, Stephen Hemminger wrote:
> The original patch used incorrect subnet range for testing.
> 
> Fixes: 37afe381bde4 ("examples/l3fwd: use reserved IP addresses")
> Reported-by: Ferruh Yigit <ferruh.yigit@intel.com>

I guess this is:
Reported-by: Hemant Agrawal <hemant.agrawal@nxp.com>

> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  doc/guides/testpmd_app_ug/run_app.rst |  6 +++---
>  examples/l3fwd/l3fwd_lpm.c            | 18 +++++++++---------
>  2 files changed, 12 insertions(+), 12 deletions(-)
> 
> diff --git a/doc/guides/testpmd_app_ug/run_app.rst b/doc/guides/testpmd_app_ug/run_app.rst
> index 00e0c2ac5152..858cec7e0b0b 100644
> --- a/doc/guides/testpmd_app_ug/run_app.rst
> +++ b/doc/guides/testpmd_app_ug/run_app.rst
> @@ -129,9 +129,9 @@ The command line options are:
>  *   ``--tx-ip=SRC,DST``
>  
>      Set the source and destination IP address used when doing transmit only test.
> -    The defaults address values are source 192.18.0.1 and
> -    destination 192.18.0.2. These are special purpose addresses
> -    reserved for benchmarking (RFC 2544).
> +    The defaults address values are source 198.18.0.1 and
> +    destination 198.18.0.2. These are special purpose addresses
> +    reserved for benchmarking (RFC 5735).
>  
>  *   ``--tx-udp=SRC[,DST]``
>  
> diff --git a/examples/l3fwd/l3fwd_lpm.c b/examples/l3fwd/l3fwd_lpm.c
> index a3a65f7fc814..349de2703cd1 100644
> --- a/examples/l3fwd/l3fwd_lpm.c
> +++ b/examples/l3fwd/l3fwd_lpm.c
> @@ -41,16 +41,16 @@ struct ipv6_l3fwd_lpm_route {
>  	uint8_t  if_out;
>  };
>  
> -/* 192.18.0.0/16 are set aside for RFC2544 benchmarking. */
> +/* 198.18.0.0/16 are set aside for RFC2544 benchmarking (RFC5735). */
>  static struct ipv4_l3fwd_lpm_route ipv4_l3fwd_lpm_route_array[] = {
> -	{RTE_IPV4(192, 18, 0, 0), 24, 0},
> -	{RTE_IPV4(192, 18, 1, 0), 24, 1},
> -	{RTE_IPV4(192, 18, 2, 0), 24, 2},
> -	{RTE_IPV4(192, 18, 3, 0), 24, 3},
> -	{RTE_IPV4(192, 18, 4, 0), 24, 4},
> -	{RTE_IPV4(192, 18, 5, 0), 24, 5},
> -	{RTE_IPV4(192, 18, 6, 0), 24, 6},
> -	{RTE_IPV4(192, 18, 7, 0), 24, 7},
> +	{RTE_IPV4(198, 18, 0, 0), 24, 0},
> +	{RTE_IPV4(198, 18, 1, 0), 24, 1},
> +	{RTE_IPV4(198, 18, 2, 0), 24, 2},
> +	{RTE_IPV4(198, 18, 3, 0), 24, 3},
> +	{RTE_IPV4(198, 18, 4, 0), 24, 4},
> +	{RTE_IPV4(198, 18, 5, 0), 24, 5},
> +	{RTE_IPV4(198, 18, 6, 0), 24, 6},
> +	{RTE_IPV4(198, 18, 7, 0), 24, 7},
>  };
>  
>  /* 2001:0200::/48 is IANA reserved range for IPv6 benchmarking (RFC5180) */
> 


  reply	other threads:[~2019-11-05 16:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-05 16:09 Stephen Hemminger
2019-11-05 16:12 ` Ferruh Yigit [this message]
2019-11-05 16:32   ` Stephen Hemminger
2019-11-06  5:36 ` Hemant Agrawal
2019-11-07 20:52   ` David Marchand
2019-11-08  3:24     ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=75e12b10-ebe0-e17d-799d-5d73956b85f2@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).