From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: gaetan.rivet@6wind.com, thomas@monjalon.net, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal/devargs: add option to supply pci dev args
Date: Tue, 5 Jun 2018 21:37:44 +0530 [thread overview]
Message-ID: <20180605160742.GB6695@jerin> (raw)
In-Reply-To: <20180605113128.15365-1-pbhagavatula@caviumnetworks.com>
-----Original Message-----
> Date: Tue, 5 Jun 2018 17:01:28 +0530
> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> To: jerin.jacob@caviumnetworks.com, gaetan.rivet@6wind.com,
> thomas@monjalon.net
> Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH] eal/devargs: add option to supply pci dev args
> X-Mailer: git-send-email 2.17.1
>
> 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 think, it would good, if we describe the side effects.
>
> Add a new eal command line option --pci-args to pass device args without
> the need to whitelist the devices.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> ---
> lib/librte_eal/common/eal_common_devargs.c | 3 +++
> lib/librte_eal/common/eal_common_options.c | 7 +++++++
> 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 +
Missed to update the eal documentation.
prev parent reply other threads:[~2018-06-05 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 11:31 Pavan Nikhilesh
2018-06-05 16:07 ` Jerin Jacob [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=20180605160742.GB6695@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.com \
--cc=pbhagavatula@caviumnetworks.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).