From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: "Walsh, Conor" <conor.walsh@intel.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/3] examples/l3fwd: print port bdf when adding routes
Date: Fri, 5 Nov 2021 07:27:17 +0000 [thread overview]
Message-ID: <PH0PR18MB40862C9DA1E7DBA9F8BCB444DE8E9@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <PH0PR11MB520729F92B50E3B2D05127D8FF8D9@PH0PR11MB5207.namprd11.prod.outlook.com>
>> From: dev <dev-bounces@dpdk.org> On Behalf Of
>> pbhagavatula@marvell.com
>> Sent: Sunday 3 October 2021 21:11
>> To: jerinj@marvell.com
>> Cc: dev@dpdk.org; Pavan Nikhilesh <pbhagavatula@marvell.com>
>> Subject: [dpdk-dev] [PATCH 2/3] examples/l3fwd: print port bdf
>when
>> adding routes
>>
>> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>>
>> Since the number of Ethernet ports have gone up, print the pci bdf
>along
>> with the routes.
>> This is also helpful for cases where allow listing order is not honored.
>>
>> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
>> ---
>> examples/l3fwd/l3fwd_fib.c | 16 ++++++++++------
>> examples/l3fwd/l3fwd_lpm.c | 9 ++++++---
>> 2 files changed, 16 insertions(+), 9 deletions(-)
>>
>> diff --git a/examples/l3fwd/l3fwd_fib.c
>b/examples/l3fwd/l3fwd_fib.c
>> index f8d6a3ac39..cc6054ca44 100644
>> --- a/examples/l3fwd/l3fwd_fib.c
>> +++ b/examples/l3fwd/l3fwd_fib.c
>> @@ -439,6 +439,7 @@ setup_fib(const int socketid)
>>
>> /* Populate the fib ipv4 table. */
>> for (i = 0; i < RTE_DIM(ipv4_l3fwd_route_array); i++) {
>> + struct rte_eth_dev_info dev_info;
>> struct in_addr in;
>>
>> /* Skip unused ports. */
>> @@ -446,6 +447,8 @@ setup_fib(const int socketid)
>> enabled_port_mask) == 0)
>> continue;
>>
>> +
> rte_eth_dev_info_get(ipv4_l3fwd_route_array[i].if_out,
>> + &dev_info);
>> ret =
>rte_fib_add(ipv4_l3fwd_fib_lookup_struct[socketid],
>> ipv4_l3fwd_route_array[i].ip,
>> ipv4_l3fwd_route_array[i].depth,
>> @@ -459,13 +462,14 @@ setup_fib(const int socketid)
>>
>> in.s_addr = htonl(ipv4_l3fwd_route_array[i].ip);
>> if (inet_ntop(AF_INET, &in, abuf, sizeof(abuf)) != NULL)
>{
>> - printf("FIB: Adding route %s / %d (%d)\n",
>> - abuf,
>> - ipv4_l3fwd_route_array[i].depth,
>> - ipv4_l3fwd_route_array[i].if_out);
>> + printf("FIB: Adding route %s / %d (%d) [%s]\n",
>abuf,
>> + ipv4_l3fwd_route_array[i].depth,
>> + ipv4_l3fwd_route_array[i].if_out,
>> + dev_info.device->name);
>> } else {
>> - printf("FIB: IPv4 route added to port %d\n",
>> - ipv4_l3fwd_route_array[i].if_out);
>> + printf("FIB: IPv4 route added to port %d
>[%s]\n",
>> + ipv4_l3fwd_route_array[i].if_out,
>> + dev_info.device->name);
>> }
>> }
>> /* >8 End of setup fib. */
>> diff --git a/examples/l3fwd/l3fwd_lpm.c
>b/examples/l3fwd/l3fwd_lpm.c
>> index 7200160164..582911c622 100644
>> --- a/examples/l3fwd/l3fwd_lpm.c
>> +++ b/examples/l3fwd/l3fwd_lpm.c
>> @@ -451,6 +451,7 @@ setup_lpm(const int socketid)
>>
>> /* populate the LPM table */
>> for (i = 0; i < RTE_DIM(ipv4_l3fwd_route_array); i++) {
>> + struct rte_eth_dev_info dev_info;
>> struct in_addr in;
>>
>> /* skip unused ports */
>> @@ -458,6 +459,8 @@ setup_lpm(const int socketid)
>> enabled_port_mask) == 0)
>> continue;
>>
>> +
> rte_eth_dev_info_get(ipv4_l3fwd_route_array[i].if_out,
>> + &dev_info);
>> ret =
>rte_lpm_add(ipv4_l3fwd_lpm_lookup_struct[socketid],
>> ipv4_l3fwd_route_array[i].ip,
>> ipv4_l3fwd_route_array[i].depth,
>> @@ -470,10 +473,10 @@ setup_lpm(const int socketid)
>> }
>>
>> in.s_addr = htonl(ipv4_l3fwd_route_array[i].ip);
>> - printf("LPM: Adding route %s / %d (%d)\n",
>> + printf("LPM: Adding route %s / %d (%d) [%s]\n",
>> inet_ntop(AF_INET, &in, abuf, sizeof(abuf)),
>> - ipv4_l3fwd_route_array[i].depth,
>> - ipv4_l3fwd_route_array[i].if_out);
>> + ipv4_l3fwd_route_array[i].depth,
>> + ipv4_l3fwd_route_array[i].if_out, dev_info.device-
>> >name);
>> }
>>
>> /* create the LPM6 table */
>
>Hi Pavan,
>
>If this is to be added it should probably print the BDF for the IPv6 routes
>as well as the IPv4 routes for consistency.
>Otherwise I think this is a good addition.
Sure, I will add it in the next version.
>
>Thanks,
>Conor.
Thanks,
Pavan.
next prev parent reply other threads:[~2021-11-05 7:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 5:23 [dpdk-dev] [PATCH 1/2] examples/l3fwd: increase number of routes pbhagavatula
2019-10-30 5:23 ` [dpdk-dev] [PATCH 2/2] examples/l3fwd: print port bdf when initializing routes pbhagavatula
2019-11-08 8:51 ` [dpdk-dev] [PATCH 1/2] examples/l3fwd: increase number of routes David Marchand
2020-08-02 18:16 ` [dpdk-dev] [PATCH v2 1/3] " pbhagavatula
2020-08-02 18:16 ` [dpdk-dev] [PATCH v2 2/3] examples/l3fwd: use IP reserved addresses for EM mode pbhagavatula
2020-10-23 14:11 ` David Marchand
2020-08-02 18:16 ` [dpdk-dev] [PATCH v2 3/3] examples/l3fwd: print port bdf when initializing routes pbhagavatula
2021-10-03 20:11 ` [dpdk-dev] [PATCH 1/3] examples/l3fwd: increase number of routes pbhagavatula
2021-10-03 20:11 ` [dpdk-dev] [PATCH 2/3] examples/l3fwd: print port bdf when adding routes pbhagavatula
2021-11-04 10:28 ` Walsh, Conor
2021-11-05 7:27 ` Pavan Nikhilesh Bhagavatula [this message]
2021-10-03 20:11 ` [dpdk-dev] [PATCH 3/3] examples/l3fwd: use reserved addresses for EM mode pbhagavatula
2021-10-03 20:24 ` [dpdk-dev] [PATCH v4 1/3] examples/l3fwd: increase number of routes pbhagavatula
2021-10-03 20:24 ` [dpdk-dev] [PATCH v4 2/3] examples/l3fwd: print port bdf when adding routes pbhagavatula
2021-10-03 20:24 ` [dpdk-dev] [PATCH v4 3/3] examples/l3fwd: use reserved addresses for EM mode pbhagavatula
2021-11-03 20:53 ` David Marchand
2021-11-05 7:30 ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2021-11-04 10:28 ` [dpdk-dev] [PATCH v4 1/3] examples/l3fwd: increase number of routes Walsh, Conor
2021-11-05 7:27 ` Pavan Nikhilesh Bhagavatula
2021-11-05 8:38 ` [dpdk-dev] [PATCH v5 " pbhagavatula
2021-11-05 8:38 ` [dpdk-dev] [PATCH v5 2/3] examples/l3fwd: print port bdf when adding routes pbhagavatula
2021-11-05 9:34 ` Walsh, Conor
2021-11-05 8:38 ` [dpdk-dev] [PATCH v5 3/3] examples/l3fwd: use reserved addresses for EM mode pbhagavatula
2021-11-16 10:03 ` David Marchand
2021-11-05 9:28 ` [dpdk-dev] [PATCH v5 1/3] examples/l3fwd: increase number of routes Walsh, Conor
2021-10-04 15:46 ` [dpdk-dev] [PATCH " 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=PH0PR18MB40862C9DA1E7DBA9F8BCB444DE8E9@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.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).