DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Varghese, Vipin" <vipin.varghese@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Pattan, Reshma" <reshma.pattan@intel.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1] app/pdump: add check for PCAP PMD
Date: Tue, 6 Mar 2018 08:45:41 +0000	[thread overview]
Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D19DE9B@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <6cb37db7-9efd-93de-0136-d327f41f9879@intel.com>

Hi Ferruh,

> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Monday, March 5, 2018 2:33 PM
> To: Varghese, Vipin <vipin.varghese@intel.com>; dev@dpdk.org; Pattan,
> Reshma <reshma.pattan@intel.com>
> Cc: Mcnamara, John <john.mcnamara@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v1] app/pdump: add check for PCAP PMD
> 
> On 3/5/2018 7:57 AM, Vipin Varghese wrote:
> > dpdk-pdump makes use of LIBRTE_PMD_PCAP for interfacing the ring to
> > the device-queue pair. Updating Makefile to check for the same.
> >
> > Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
> > ---
> >  app/pdump/Makefile | 4 ++++
> >  1 file changed, 4 insertions(+)
> >
> > diff --git a/app/pdump/Makefile b/app/pdump/Makefile index
> > bd3c208..038a34f 100644
> > --- a/app/pdump/Makefile
> > +++ b/app/pdump/Makefile
> > @@ -3,6 +3,10 @@
> >
> >  include $(RTE_SDK)/mk/rte.vars.mk
> >
> > +ifeq ($(CONFIG_RTE_LIBRTE_PMD_PCAP),n) $(error "Please enable
> > +CONFIG_RTE_LIBRTE_PMD_PCAP") endif
> 
> pdump is enabled default, so won't this break the default build?

Yes, you are right it will fail. Which then forces the user to enable PCAP.

> 
> What about moving this to lib/librte_pdump, convert $(error ..) to $(warning ..)
> and disable CONFIG_RTE_LIBRTE_PDUMP there?

If we set to warning and there are no PCAP headers in build system. The application gets built, but will fail internally becz the pcap API will fails during execution.

> 
> > +
> >  ifeq ($(CONFIG_RTE_LIBRTE_PDUMP),y)
> >
> >  APP = dpdk-pdump
> >


  reply	other threads:[~2018-03-06  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05  7:57 Vipin Varghese
2018-03-05 14:32 ` Ferruh Yigit
2018-03-06  8:45   ` Varghese, Vipin [this message]
2018-03-06 11:57     ` Ferruh Yigit
2018-03-06 12:12 ` Pattan, Reshma
2018-03-12 17:46   ` Varghese, Vipin

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=4C9E0AB70F954A408CC4ADDBF0F8FA7D4D19DE9B@BGSMSX101.gar.corp.intel.com \
    --to=vipin.varghese@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=reshma.pattan@intel.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).