DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev <dev@dpdk.org>, Chengwen Feng <fengchengwen@huawei.com>,
	 Aaron Conole <aconole@redhat.com>,
	Michael Santana <maicolgabriel@hotmail.com>,
	Ciara Power <ciara.power@intel.com>
Subject: Re: [PATCH] app/test: invoke all telemetry commands
Date: Fri, 29 Jul 2022 15:42:10 +0200	[thread overview]
Message-ID: <CAJFAV8wb2PQ_B70zNnL1v4EbjG2Wea82y6WvBkN5k8eD5ih1Gw@mail.gmail.com> (raw)
In-Reply-To: <YuPgRqS4XMLFeOAb@bricha3-MOBL.ger.corp.intel.com>

On Fri, Jul 29, 2022 at 3:27 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
> > > Rather than looping for each driver and building a huge cmdline, we should
> > > just be able to pass in the path to the drivers directory, and have DPDK
> > > auto-load all .so files there. Passing in "meson.project_build_root() +
> > > '/drivers'" should probably work. If we want a more correct way to get the
> > > drivers build directory, we can call meson.current_build_dir() when
> > > processing the drivers and save off that value to be reused here.
> >
> > Or simply resolve this with a:
> > test_args += ['-d', fs.parent(dpdk_drivers[0].full_path())]
> >
> > But the problem is that the fs meson module comes with version 0.53 afaics.
> > Any elegant alternative idea?
> >
> I think the approach you have taken in the v2 is best.

I'm happy that you like your own suggestion ;-).
Joke aside, thanks Bruce.


-- 
David Marchand


  reply	other threads:[~2022-07-29 13:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  9:54 David Marchand
2022-07-29 10:20 ` Bruce Richardson
2022-07-29 11:13   ` David Marchand
2022-07-29 11:28     ` Bruce Richardson
2022-07-29 11:53   ` David Marchand
2022-07-29 13:27     ` Bruce Richardson
2022-07-29 13:42       ` David Marchand [this message]
2022-07-29 12:42 ` [PATCH v2 1/2] app/test: load drivers using build directory David Marchand
2022-07-29 12:42   ` [PATCH v2 2/2] app/test: invoke all telemetry commands David Marchand
2022-07-29 18:04     ` Aaron Conole
2022-08-16 16:20     ` Power, Ciara
2022-08-26  9:42       ` David Marchand
2022-07-29 13:28   ` [PATCH v2 1/2] app/test: load drivers using build directory Bruce Richardson

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=CAJFAV8wb2PQ_B70zNnL1v4EbjG2Wea82y6WvBkN5k8eD5ih1Gw@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.power@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=maicolgabriel@hotmail.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).