From: Thomas Monjalon <thomas@monjalon.net>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Cc: David Marchand <david.marchand@redhat.com>,
dev@dpdk.org, Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Ori Kam <orika@mellanox.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Radu Nicolau <radu.nicolau@intel.com>,
Akhil Goyal <akhil.goyal@nxp.com>,
Tomasz Kantecki <tomasz.kantecki@intel.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] examples/l3fwd: increase number of routes
Date: Thu, 30 Jul 2020 23:28:43 +0200 [thread overview]
Message-ID: <3046806.VFRClzR3Of@thomas> (raw)
In-Reply-To: <CY4PR1801MB18631C685E135636773E6089DE740@CY4PR1801MB1863.namprd18.prod.outlook.com>
11/11/2019 08:46, Pavan Nikhilesh Bhagavatula:
> >On Wed, Oct 30, 2019 at 6:23 AM <pbhagavatula@marvell.com> wrote:
> >>
> >> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> >>
> >> Increase the number of routes from 8 to 16 that are statically added
> >for
> >> lpm and em mode as most of the SoCs support more than 8
> >interfaces.
> >>
> >> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> >> ---
> >> examples/l3fwd/l3fwd_em.c | 72
> >++++++++++++++++++++++++++++++++++++++
> >> examples/l3fwd/l3fwd_lpm.c | 16 +++++++++
> >> 2 files changed, 88 insertions(+)
> >>
> >> diff --git a/examples/l3fwd/l3fwd_em.c
> >b/examples/l3fwd/l3fwd_em.c
> >> index 74a7c8fa4..c07a5b937 100644
> >> --- a/examples/l3fwd/l3fwd_em.c
> >> +++ b/examples/l3fwd/l3fwd_em.c
> >> @@ -103,6 +103,18 @@ static struct ipv4_l3fwd_em_route
> >ipv4_l3fwd_em_route_array[] = {
> >> {{RTE_IPV4(201, 0, 0, 0), RTE_IPV4(200, 20, 0, 1), 102, 12,
> >IPPROTO_TCP}, 1},
> >> {{RTE_IPV4(111, 0, 0, 0), RTE_IPV4(100, 30, 0, 1), 101, 11,
> >IPPROTO_TCP}, 2},
> >> {{RTE_IPV4(211, 0, 0, 0), RTE_IPV4(200, 40, 0, 1), 102, 12,
> >IPPROTO_TCP}, 3},
> >> + {{RTE_IPV4(121, 0, 0, 0), RTE_IPV4(100, 10, 0, 1), 101, 11,
> >IPPROTO_TCP}, 4},
> >> + {{RTE_IPV4(221, 0, 0, 0), RTE_IPV4(200, 20, 0, 1), 102, 12,
> >IPPROTO_TCP}, 5},
> >> + {{RTE_IPV4(131, 0, 0, 0), RTE_IPV4(100, 30, 0, 1), 101, 11,
> >IPPROTO_TCP}, 6},
> >> + {{RTE_IPV4(231, 0, 0, 0), RTE_IPV4(200, 40, 0, 1), 102, 12,
> >IPPROTO_TCP}, 7},
> >> + {{RTE_IPV4(141, 0, 0, 0), RTE_IPV4(100, 30, 0, 1), 101, 11,
> >IPPROTO_TCP}, 8},
> >> + {{RTE_IPV4(241, 0, 0, 0), RTE_IPV4(200, 40, 0, 1), 102, 12,
> >IPPROTO_TCP}, 9},
> >> + {{RTE_IPV4(151, 0, 0, 0), RTE_IPV4(100, 30, 0, 1), 101, 11,
> >IPPROTO_TCP}, 10},
> >> + {{RTE_IPV4(251, 0, 0, 0), RTE_IPV4(200, 40, 0, 1), 102, 12,
> >IPPROTO_TCP}, 11},
> >> + {{RTE_IPV4(161, 0, 0, 0), RTE_IPV4(100, 30, 0, 1), 101, 11,
> >IPPROTO_TCP}, 12},
> >> + {{RTE_IPV4(261, 0, 0, 0), RTE_IPV4(200, 40, 0, 1), 102, 12,
> >IPPROTO_TCP}, 13},
> >
> >Am I reading this correctly ? 261.0.0.0 ?
>
> My bad. Do you think it's better to change the address to 198.18.0.0/15 block as it
> would be inline with RFC as well as LPM addresses?
After 9 months, I think you could send a v2 ;)
next prev parent reply other threads:[~2020-07-30 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 7:46 [dpdk-dev] [PATCH 1/2] examples/l3fwd: increase number of routes Pavan Nikhilesh Bhagavatula
2020-07-30 21:28 ` Thomas Monjalon [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-30 5:23 pbhagavatula
2019-11-08 8:51 ` David Marchand
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=3046806.VFRClzR3Of@thomas \
--to=thomas@monjalon.net \
--cc=akhil.goyal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=marko.kovacevic@intel.com \
--cc=orika@mellanox.com \
--cc=pbhagavatula@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=tomasz.kantecki@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.