From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
To: Shahaf Shuler <shahafs@mellanox.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
"gaetan.rivet@6wind.com" <gaetan.rivet@6wind.com>,
Thomas Monjalon <thomas@monjalon.net>,
ferruh.yigit@intel.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] eal/devargs: add option to supply PCI dev args
Date: Tue, 10 Jul 2018 15:37:27 +0530 [thread overview]
Message-ID: <20180710100726.GA30393@ltp-pvn> (raw)
In-Reply-To: <DB7PR05MB44263B4166F9091A0719B7B3C3490@DB7PR05MB4426.eurprd05.prod.outlook.com>
Hi Shahaf,
On Tue, Jun 26, 2018 at 12:48:49PM +0000, Shahaf Shuler wrote:
> Hi Pavan,
>
> Friday, June 15, 2018 7:44 AM, Pavan Nikhilesh:
> > Subject: [dpdk-dev] [PATCH v2] eal/devargs: add option to supply PCI dev
> > args
> >
> > Currently, the only way of supplying device argument to a pci device is to
> > whitelist it i.e. -w 000X:00:0X.0,self_test=1. This is not a very feasible method
> > as whitelisting a device has its own side effects i.e only the whitelisted pci
> > devices are probed.
> >
> > Add a new eal command line option --pci-args to pass device args without the
> > need to whitelist the devices.
> > --pci-args 000X:00:0X.0,self_test=1
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>
> Tested-by: Shahaf Shuler <shahafs@mellanox.com>
>
> It seems to work.
> Please see small comments below
>
> > ---
> > v2 Changes:
> > - Document the option usage in eal_common_usage.
> > - Update commit log to be more informative.
> >
> > lib/librte_eal/common/eal_common_devargs.c | 3 +++
> > lib/librte_eal/common/eal_common_options.c | 9 +++++++++
> > lib/librte_eal/common/eal_options.h | 2 ++
> > lib/librte_eal/common/include/rte_dev.h | 1 +
> > lib/librte_eal/common/include/rte_devargs.h | 1 +
> > 5 files changed, 16 insertions(+)
>
> Should we also update the manual of testpmd (doc/guides/testpmd_app_ug/run_app.rst ) for the new eal arg?
I was wondering where exactly this has to be documented, Thanks for pointing it
out I will add it in the next version.
>
> >
> > };
> > diff --git a/lib/librte_eal/common/include/rte_devargs.h
> > b/lib/librte_eal/common/include/rte_devargs.h
> > index 58fbd90a2..78c600bf2 100644
> > --- a/lib/librte_eal/common/include/rte_devargs.h
> > +++ b/lib/librte_eal/common/include/rte_devargs.h
> > @@ -29,6 +29,7 @@ extern "C" {
> > * Type of generic device
> > */
> > enum rte_devtype {
> > + RTE_DEVTYPE_NORMAL, /* Normal dev with special pci args */
>
> What is "Normal" device? Can we find a better name?
Maybe something like RTE_DEVTYPE_PCI would fit in?. Let me know if you have any
suggestions.
>
> > RTE_DEVTYPE_WHITELISTED_PCI,
> > RTE_DEVTYPE_BLACKLISTED_PCI,
> > RTE_DEVTYPE_VIRTUAL,
> > --
> > 2.17.1
>
Thanks,
Pavan.
prev parent reply other threads:[~2018-07-10 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-15 4:43 Pavan Nikhilesh
2018-06-26 12:48 ` Shahaf Shuler
2018-06-26 15:40 ` Ferruh Yigit
2018-06-27 8:39 ` Gaëtan Rivet
2018-06-27 8:55 ` Pavan Nikhilesh
2018-06-27 9:57 ` Gaëtan Rivet
2018-07-10 10:19 ` Pavan Nikhilesh
2018-07-15 22:25 ` Thomas Monjalon
2018-07-16 11:05 ` Pavan Nikhilesh
2018-07-16 12:14 ` Thomas Monjalon
2018-07-10 10:07 ` Pavan Nikhilesh [this message]
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=20180710100726.GA30393@ltp-pvn \
--to=pbhagavatula@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gaetan.rivet@6wind.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=shahafs@mellanox.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 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).