DPDK usage discussions
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles@intel.com>
To: Alessio Silvestro <alessio.silvestro@neclab.eu>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK 17.11-rc2 and Pktgen 3.4.2 make error
Date: Tue, 7 Nov 2017 16:25:11 +0000	[thread overview]
Message-ID: <213E580E-CE31-4136-A090-4F1A9467733F@intel.com> (raw)
In-Reply-To: <EC16299E2457374CA72AA8DDEB24D6CF3BBEFD0F@PALLENE.office.hd>



> On Nov 7, 2017, at 9:18 AM, Alessio Silvestro <alessio.silvestro@neclab.eu> wrote:
> 
> Dear all,
> 
> I have debian (4.13.0-0.bpo.1-amd64) and dpdk 17.11-rc2.
> 
> I am trying to install pktgen (3.4.2), but when I do make I got the following error:
> 
> 
> CC cli-functions.o
> In file included from /usr/local/pktgen-3.4.2/app/pktgen.h:112:0,
>                 from /usr/local/pktgen-3.4.2/app/cli-functions.c:57:
> /usr/local/pktgen-3.4.2/app/pktgen-port-cfg.h: In function Өpktgen_dump_dev_infoӮ:
> /usr/local/pktgen-3.4.2/app/pktgen-port-cfg.h:327:28: error: dereferencing pointer to incomplete type Өstruct rte_pci_deviceӮ
>   di->pci_dev ? di->pci_dev->max_vfs : 0,


The problem is that we have changed the PCI code, I have fix for this, but it needs to be cleaned up and pushed but I am having some bandwidth problems.

In the pktgen-port-cfg.h file at line 327 you need to add a #if around the first fprintf().

#if RTE_VERSION < RTE_VERSION_NUM(17, 5, 0, 0)
	fprintf( …
		);
#endif

Maybe other ones in the code too. I will try to find some time to push that patch.

>                            ^~
> /usr/local/pktgen-3.4.2/app/pktgen-port-cfg.h:343:25: warning: format Ө%dӮ expects argument of type ӨintӮ, but argument 3 has type Өuint64_t {aka long unsigned int}Ӯ [-Wformat=]
>   "   rx_offload_capa:%4d, tx_offload_capa   :%4d, reta_size     :%6d, flow_type_rss_offloads:%016" PRIx64 "\n",
>                         ^
> /usr/local/pktgen-3.4.2/app/pktgen-port-cfg.h:343:49: warning: format Ө%dӮ expects argument of type ӨintӮ, but argument 4 has type Өuint64_t {aka long unsigned int}Ӯ [-Wformat=]
>   "   rx_offload_capa:%4d, tx_offload_capa   :%4d, reta_size     :%6d, flow_type_rss_offloads:%016" PRIx64 "\n",
> 
> Do you have any hint or patch to suggest?
> 
> Thanks,
> Alessio
> 
> 
> ===============================================
> Alessio Silvestro             „¢„ģ„Ć„·„Ŗ””„·„ė„Ł„¹„Č„ķ
> Early Stage Researcher
> 
> Phone: +49 (0) 6221 4342 ØC 134
> e-mail: Alessio.Silvestro@neclab.eu<mailto:Alessio.Silvestro@neclab.eu>
> 
> Data Science and System Platform Research Division NEC Europe Ltd.
> Nec Laboratories Europe
> Kurfعrsten-Anlage 36, 69115 Heidelberg, Germany
> ===============================================
> NEC Europe Ltd | Registered Office: Athene, Odyssey Business Park, West End  Road, London, HA4 6QE, GB | Registered in England 2832014
> 
> 

Regards,
Keith


  reply	other threads:[~2017-11-07 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07 15:18 Alessio Silvestro
2017-11-07 16:25 ` Wiles, Keith [this message]
2017-11-07 16:26   ` Wiles, Keith
2017-11-07 17:13     ` Alessio Silvestro
2017-11-08  9:21       ` Gaëtan Rivet
2017-11-08  9:51         ` Alessio Silvestro
2017-11-08 13:08         ` Wiles, Keith

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=213E580E-CE31-4136-A090-4F1A9467733F@intel.com \
    --to=keith.wiles@intel.com \
    --cc=alessio.silvestro@neclab.eu \
    --cc=users@dpdk.org \
    /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).