From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Shijith Thotton <sthotton@marvell.com>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"david.marchand@redhat.com" <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re: compilation time of cnxk event driver
Date: Mon, 8 Nov 2021 11:32:14 +0000 [thread overview]
Message-ID: <PH0PR18MB4086DC237667F991D6A9AEF1DE919@PH0PR18MB4086.namprd18.prod.outlook.com> (raw)
In-Reply-To: <4cad50cc-f929-0300-0322-866bcd8712bc@intel.com>
Hi Thomas, Ferruh,
We need to further split Rx/Tx functions in both net/cnxk and event/cnxk to enable more parallelism.
This is planned for the next release.
Thanks,
Pavan.
>-----Original Message-----
>From: Ferruh Yigit <ferruh.yigit@intel.com>
>Sent: Monday, November 8, 2021 2:26 PM
>To: Thomas Monjalon <thomas@monjalon.net>; Pavan Nikhilesh
>Bhagavatula <pbhagavatula@marvell.com>; Shijith Thotton
><sthotton@marvell.com>
>Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>;
>david.marchand@redhat.com; dev@dpdk.org
>Subject: [EXT] Re: [dpdk-dev] compilation time of cnxk event driver
>
>External Email
>
>----------------------------------------------------------------------
>On 11/7/2021 9:35 PM, Thomas Monjalon wrote:
>> Hi,
>>
>> It seems compilation time of drivers/event/cnxk is getting very long.
>> Please could you look at it?
>>
>
>ack, I also recognized it. Various builds all stuck on same a few files.
next prev parent reply other threads:[~2021-11-08 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 21:35 [dpdk-dev] " Thomas Monjalon
2021-11-08 8:56 ` Ferruh Yigit
2021-11-08 11:32 ` Pavan Nikhilesh Bhagavatula [this message]
2021-11-11 14:18 ` [dpdk-dev] [EXT] " Nipun Gupta
2021-11-11 14:21 ` Pavan Nikhilesh Bhagavatula
2021-11-11 14:28 ` Nipun Gupta
2021-11-26 14:00 ` [EXT] Re: [dpdk-dev] " 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=PH0PR18MB4086DC237667F991D6A9AEF1DE919@PH0PR18MB4086.namprd18.prod.outlook.com \
--to=pbhagavatula@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=sthotton@marvell.com \
--cc=thomas@monjalon.net \
/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).