From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Shijith Thotton <sthotton@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>, dpdk-dev <dev@dpdk.org>
Subject: Re: [PATCH v2 8/8] net/cnxk: add CN10K template Tx functions to build
Date: Mon, 24 Jan 2022 12:01:10 +0000 [thread overview]
Message-ID: <274453ca-7d4b-512a-2f02-c7351cb2eeda@intel.com> (raw)
In-Reply-To: <602f3799-5ebd-8043-d3a5-94d8df446bd7@intel.com>
On 1/24/2022 9:52 AM, Ferruh Yigit wrote:
> On 1/23/2022 11:59 AM, Jerin Jacob wrote:
>> On Thu, Jan 20, 2022 at 8:23 PM<pbhagavatula@marvell.com> wrote:
>>> From: Pavan Nikhilesh<pbhagavatula@marvell.com>
>>>
>>> Add CN10K segregated Tx and event Tx template functions to build,
>>> add macros to make future modifications simpler.
>>>
>>> Signed-off-by: Pavan Nikhilesh<pbhagavatula@marvell.com>
>> Series Acked-by: Jerin Jacob<jerinj@marvell.com>
>> Tested and captured build time improvement at [3].
>>
>> Series applied to dpdk-next-net-mrvl/for-next-net with following
>> changes[2]. Thanks.
>>
>> Hi Ferruh.
>> Noticed ICC failure with this patch[1]. Not sure is this a CI issue or
>> not? I don't have set up with ICC. If it some ICC compiler issue then
>> it is OK to remove ICC build support for cnxk drivers.
>>
>
> Error is file not found [3]? Something may be wrong in the environment,
> I will test.
>
I can't able to test. Intel is switching to 'oneapi' toolset, that is why
ICC is not updated for a while, and after OS update ICC doesn't work well
with stdlib in my system.
I suggest ignoring this ICC error, since there is no reported code issue,
and we can think ICC support in DPDK altogether.
>
>
>> [1]
>> http://mails.dpdk.org/archives/test-report/2022-January/253920.html
>>
>> [2]
>> - Changed CN9K/CN10K to cn9k/cn10k in commit messages
>> - Removed extra line from meson.build.
>
> [3]
> icc: error #10236: File not found: ''-Wl,-rpath,$ORIGIN/../lib:$ORIGIN/''
next prev parent reply other threads:[~2022-01-24 12:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 14:51 [PATCH v2 1/8] net/cnxk: add CN9K segregated Rx functions pbhagavatula
2022-01-20 14:51 ` [PATCH v2 2/8] net/cnxk: add CN9K template Rx functions to build pbhagavatula
2022-01-20 14:51 ` [PATCH v2 3/8] net/cnxk: add CN9K segregated Tx functions pbhagavatula
2022-01-20 14:51 ` [PATCH v2 4/8] net/cnxk: add CN9K template Tx functions to build pbhagavatula
2022-01-20 14:51 ` [PATCH v2 5/8] net/cnxk: add CN10K segregated Rx functions pbhagavatula
2022-01-20 14:51 ` [PATCH v2 6/8] net/cnxk: add CN10K template Rx functions to build pbhagavatula
2022-01-20 14:51 ` [PATCH v2 7/8] net/cnxk: add CN10K segregated Tx functions pbhagavatula
2022-01-20 14:51 ` [PATCH v2 8/8] net/cnxk: add CN10K template Tx functions to build pbhagavatula
2022-01-23 11:59 ` Jerin Jacob
2022-01-24 9:52 ` Ferruh Yigit
2022-01-24 10:18 ` Ferruh Yigit
2022-01-24 11:56 ` Jerin Jacob
2022-01-24 12:01 ` Ferruh Yigit [this message]
2022-01-21 15:23 ` [PATCH v2 1/8] net/cnxk: add CN9K segregated Rx functions Jerin Jacob
2022-01-22 15:48 ` [PATCH v3 " pbhagavatula
2022-01-22 15:48 ` [PATCH v3 2/8] net/cnxk: add CN9K template Rx functions to build pbhagavatula
2022-01-22 15:48 ` [PATCH v3 3/8] net/cnxk: add CN9K segregated Tx functions pbhagavatula
2022-01-22 15:48 ` [PATCH v3 4/8] net/cnxk: add CN9K template Tx functions to build pbhagavatula
2022-01-22 15:48 ` [PATCH v3 5/8] net/cnxk: add CN10K segregated Rx functions pbhagavatula
2022-01-22 15:48 ` [PATCH v3 6/8] net/cnxk: add CN10K template Rx functions to build pbhagavatula
2022-01-22 15:48 ` [PATCH v3 7/8] net/cnxk: add CN10K segregated Tx functions pbhagavatula
2022-01-22 15:48 ` [PATCH v3 8/8] net/cnxk: add CN10K template Tx functions to build pbhagavatula
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=274453ca-7d4b-512a-2f02-c7351cb2eeda@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=sthotton@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).