DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Jingjing Wu <jingjing.wu@intel.com>,
	pablo.de.lara.guarch@intel.com
Subject: Re: [dpdk-dev] [RFC] testpmd: use RFC2544 reserved IP addresses
Date: Wed, 04 Apr 2018 17:37:58 +0200	[thread overview]
Message-ID: <2854179.edOHD48eUJ@xps> (raw)
In-Reply-To: <20180321034436.4089-1-stephen@networkplumber.org>

+Cc maintainers

21/03/2018 04:44, Stephen Hemminger:
> Change the transmit only side of testpmd to use the IP addresses
> that are marked as reserved for benchmarking by RFC2544 192.18.0.0/27;
> rather than the commonly used subnet 192.168.0.0/24 which is likely
> to used for administrative interface.
> 
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  app/test-pmd/txonly.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/app/test-pmd/txonly.c b/app/test-pmd/txonly.c
> index 1f08b6ed37a2..22785bdcbe44 100644
> --- a/app/test-pmd/txonly.c
> +++ b/app/test-pmd/txonly.c
> @@ -43,8 +43,9 @@
>  #define UDP_SRC_PORT 1024
>  #define UDP_DST_PORT 1024
>  
> -#define IP_SRC_ADDR ((192U << 24) | (168 << 16) | (0 << 8) | 1)
> -#define IP_DST_ADDR ((192U << 24) | (168 << 16) | (0 << 8) | 2)
> +/* RFC 2544 reserved IP addresses for benchmarking */
> +#define IP_SRC_ADDR ((192U << 24) | (18 << 16) | (0 << 8) | 1)
> +#define IP_DST_ADDR ((192U << 24) | (18 << 16) | (0 << 8) | 2)
>  
>  #define IP_DEFTTL  64   /* from RFC 1340. */
>  #define IP_VERSION 0x40
> 

  reply	other threads:[~2018-04-04 15:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21  3:44 Stephen Hemminger
2018-04-04 15:37 ` Thomas Monjalon [this message]
2018-06-07 12:52 ` Iremonger, Bernard
2018-06-08  0:07   ` Stephen Hemminger
2018-06-08  9:10     ` Iremonger, Bernard

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=2854179.edOHD48eUJ@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=wenzhuo.lu@intel.com \
    /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).