All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nipun Gupta <nipun.gupta@nxp.com>
To: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>,
	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>, Rohit Raj <rohit.raj@nxp.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: RE: [dpdk-dev] [EXT] Re:  compilation time of cnxk event driver
Date: Thu, 11 Nov 2021 14:28:23 +0000	[thread overview]
Message-ID: <DB9PR04MB84291EA2FAA293E3EB293DADE6949@DB9PR04MB8429.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <PH0PR18MB4086B4E00A8F45721125C3A3DE949@PH0PR18MB4086.namprd18.prod.outlook.com>

Thanks for the info !!
We can manually disable the drivers if compiling with this version

Regards,
Nipun

> -----Original Message-----
> From: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
> Sent: Thursday, November 11, 2021 7:51 PM
> To: Nipun Gupta <nipun.gupta@nxp.com>; 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; dev@dpdk.org; Rohit Raj <rohit.raj@nxp.com>;
> Hemant Agrawal <hemant.agrawal@nxp.com>
> Subject: RE: [dpdk-dev] [EXT] Re: compilation time of cnxk event driver
> 
> >
> >Hi Pavan,
> >
> >Compilation of cnxk (both net and event) is also broken on top of the
> >tree with aarch64-linux-gnu-gcc(gcc version 7.5.0 (Linaro GCC 7.5->
> >2019.12)).
> 
> Buggy compiler.
> See,
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.dpd
> k.org%2Fshow_bug.cgi%3Fid%3D697&amp;data=04%7C01%7Cnipun.gupta%40
> nxp.com%7C36e8cc86950f4eedd66708d9a51e8858%7C686ea1d3bc2b4c6fa92c
> d99c5c301635%7C0%7C0%7C637722372842929752%7CUnknown%7CTWFpbGZ
> sb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0
> %3D%7C1000&amp;sdata=wnW8s%2FnwHEKVznbKgwKbv6XAT3AGYLCUBLyghC
> 11yRE%3D&amp;reserved=0
> 
> >
> >Below are the error logs which are observed:
> >
> >FAILED:
> >drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_deq.c.
> >o
> >aarch64-linux-gnu-gcc -Idrivers/libtmp_rte_event_cnxk.a.p -Idrivers -
> >I../drivers -Idrivers/event/cnxk -I../drivers/event/cnxk -Ilib/eventdev -
> >I../lib/eventdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -
> >I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -
> >Ilib/eal/arm/include -I../lib/eal/arm/include -Ilib/eal/common -
> >I../lib/eal/common -Ilib/eal -I../lib/eal -Ilib/kvargs -I../lib/kvargs -
> >Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/ring -
> >I../lib/ring -Ilib/ethdev -I../lib/ethdev -Ilib/net -I../lib/net -Ilib/mbuf -
> >I../lib/mbuf -Ilib/mempool -I../lib/mempool -Ilib/meter -I../lib/meter -
> >Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -Ilib/timer -I../lib/timer -
> >Ilib/cryptodev -I../lib/cryptodev -Idrivers/bus/pci -I../drivers/bus/pci -
> >I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/common/cnxk -
> >I../drivers/common/cnxk -Ilib/security -I../lib/security -
> >Idrivers/net/cnxk -I../drivers/net/cnxk -Idrivers/bus/vdev -
> >I../drivers/bus/vdev -Idrivers/mempool/cnxk -
> >I../drivers/mempool/cnxk -Idrivers/crypto/cnxk -
> >I../drivers/crypto/cnxk -fdiagnostics-color=always -pipe -
> >D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -O3 -include rte_config.h -
> >Wextra -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -
> >Wformat-security -Wmissing-declarations -Wmissing-prototypes -
> >Wnested-externs -Wold-style-definition -Wpointer-arith -Wsign-
> >compare -Wstrict-prototypes -Wundef -Wwrite-strings -Wno-missing-
> >field-initializers -D_GNU_SOURCE -fPIC -march=armv8-a+crc -
> >DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-
> >truncation -flax-vector-conversions -Wno-strict-aliasing -
> >DRTE_LOG_DEFAULT_LOGTYPE=pmd.event.cnxk -MD -MQ
> >drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_deq.c.
> >o -MF
> >drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_deq.c.
> >o.d -o
> >drivers/libtmp_rte_event_cnxk.a.p/event_cnxk_cn10k_worker_deq.c.
> >o -c ../drivers/event/cnxk/cn10k_worker_deq.c
> >{standard input}: Assembler messages:
> >{standard input}:292: Error: reg pair must start from even reg at
> >operand 1 -- `caspl x25,x26,x25,x26,[x2]'
> >{standard input}:1221: Error: reg pair must start from even reg at
> >operand 1 -- `caspl x25,x26,x25,x26,[x2]'
> >{standard input}:1879: Error: reg pair must start from even reg at
> >operand 1 -- `caspl x9,x10,x9,x10,[x2]'
> >{standard input}:2897: Error: reg pair must start from even reg at
> >operand 1 -- `caspl x9,x10,x9,x10,[x2]'
> >{standard input}:4249: Error: reg pair must start from even reg at
> >operand 1 -- `caspl x25,x26,x25,x26,[x2]'
> >{standard input}:5262: Error: reg pair must start from even reg at
> >operand 1 -- `caspl x25,x26,x25,x26,[x2]'
> >
> >Regards,
> >Nipun
> >
> >> -----Original Message-----
> >> From: dev <dev-bounces@dpdk.org> On Behalf Of Pavan Nikhilesh
> >Bhagavatula
> >> Sent: Monday, November 8, 2021 5:02 PM
> >> 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; dev@dpdk.org
> >> Subject: Re: [dpdk-dev] [EXT] Re: compilation time of cnxk event
> >driver
> >>
> >> 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.

  reply	other threads:[~2021-11-11 14:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-07 21:35 [dpdk-dev] compilation time of cnxk event driver Thomas Monjalon
2021-11-08  8:56 ` Ferruh Yigit
2021-11-08 11:32   ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2021-11-11 14:18     ` Nipun Gupta
2021-11-11 14:21       ` Pavan Nikhilesh Bhagavatula
2021-11-11 14:28         ` Nipun Gupta [this message]
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=DB9PR04MB84291EA2FAA293E3EB293DADE6949@DB9PR04MB8429.eurprd04.prod.outlook.com \
    --to=nipun.gupta@nxp.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.com \
    --cc=rohit.raj@nxp.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 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.