DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] testpmd: use RFC2544 reserved IP addresses
Date: Thu, 7 Jun 2018 17:07:45 -0700	[thread overview]
Message-ID: <20180607170745.0eac95bd@xeon-e3> (raw)
In-Reply-To: <8CEF83825BEC744B83065625E567D7C260CAF443@IRSMSX108.ger.corp.intel.com>

On Thu, 7 Jun 2018 12:52:59 +0000
"Iremonger, Bernard" <bernard.iremonger@intel.com> wrote:

> Hi Stephen,
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
> > Sent: Wednesday, March 21, 2018 3:45 AM
> > To: dev@dpdk.org
> > Cc: Stephen Hemminger <stephen@networkplumber.org>
> > Subject: [dpdk-dev] [RFC] testpmd: use RFC2544 reserved IP addresses
> > 
> > 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  
> 
> RFC2544 seems to use 198.18.0.0 and 198.19.0.0 ?

The 18 and 19 networks would be used when doing L3fwd type test.
The addresses this patch addresses are those used in the default case
for a transmit only type of test (on same subnet).

> 
> > the commonly used subnet 192.168.0.0/24 which is likely to used for
> > administrative interface.  
> 
> Typo in the commit message "to used" should be "to be used"

yes.

> 
> > 
> > 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
> > --
> > 2.16.2  
> 
> From RFC 2544:
> "The single filter case should permit traffic from IP address  198.18.1.2 to IP address 198.19.65.2 and deny all other traffic."
> 
> Should the macros be as follows?
> #define IP_SRC_ADDR ((198U << 24) | (18 << 16) | (0 << 8) | 1)
> #define IP_DST_ADDR ((198U << 24) | (19 << 16) | (0 << 8) | 2)
> 
> Regards,
> 
> Bernard
> 

  reply	other threads:[~2018-06-08  0:07 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
2018-06-07 12:52 ` Iremonger, Bernard
2018-06-08  0:07   ` Stephen Hemminger [this message]
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=20180607170745.0eac95bd@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.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).